Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1432903 - Set GssProxy options to enable caching of ldap tickets
Set GssProxy options to enable caching of ldap tickets
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: IPA Maintainers
Abhijeet Kasurde
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-16 07:12 EDT by Petr Vobornik
Modified: 2017-08-01 05:46 EDT (History)
8 users (show)

See Also:
Fixed In Version: ipa-4.5.0-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 05:46:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2304 normal SHIPPED_LIVE ipa bug fix and enhancement update 2017-08-01 08:41:35 EDT

  None (edit)
Description Petr Vobornik 2017-03-16 07:12:46 EDT
When using gssproxy we need to enable syncing back ccaches. This allows the framework to receive back and store (in encrypted form) the ldap/ ticket acquire to talk to the directory server. Without this option each connection to the ldap server will cause a new rountrip to the KDC to acquire a new ldap/ ticket. This will increase the load on both the KDC and DS (to search the principal keys) as well as slow down each operation for the framework.
Comment 1 Petr Vobornik 2017-03-16 07:13:50 EDT
Upstream ticket: https://pagure.io/freeipa/issue/6771
Comment 2 Petr Vobornik 2017-03-16 07:15:15 EDT
Needed for IPA to be performant.
Comment 3 Martin Babinsky 2017-03-16 08:11:45 EDT
Fixed upstream
master:
https://pagure.io/freeipa/c/4ee7e4ee6d6500d8b8935c9033388adc4cdbe672
Comment 4 Jan Cholasta 2017-03-21 07:06:28 EDT
Fixed upstream
ipa-4-5:
https://pagure.io/freeipa/c/62d39385e20b3e1b059466f37cc063833355551e
Comment 7 Simo Sorce 2017-06-06 06:12:27 EDT
The difference between the option turned off and turned on is that when the option is turned off each request to the LDAP server requires a roundtripto the KDC to acquire an LDAP ticket, while that is not necessary with the option tunerd on.

So to test you can simply compare two runs (before and after) where you use the IPA API (either vina ipa command or via web UI) to perform a number of operations as a specific test user.

With the option turned off you should see in krb5kdc.log a request for an ldap/<ipa-server> ticket by 'test' user for each operation.
Withthe option turned on you should see only one (or few) request in krb5kdc.log for all operations.

HTH.
Comment 8 Simo Sorce 2017-06-06 06:13:02 EDT
See instructions above
Comment 9 Abhijeet Kasurde 2017-06-06 06:41:19 EDT
Verified using IPA version :: ipa-server-4.5.0-14.el7.x86_64

Marking BZ as verified. 

Performed sanity tests and integration tests for verification. 

As per Comment #7, seen only single ldap/<server> request for all operations.

# tail -f /var/log/krb4kdc.log
Jun 06 06:34:13 ipaserver01.testrelm.test krb5kdc[16265](info): TGS_REQ (8 etypes {18 17 20 19 16 23 25 26}) 10.19.34.11: ISSUE: authtime 1496744877, etypes {rep=18 tkt=18 ses=18}, HTTP/ipaserver01.testrelm.test@TESTRELM.TEST for ldap/ipaserver01.testrelm.test@TESTRELM.TEST
Jun 06 06:34:13 ipaserver01.testrelm.test krb5kdc[16265](info): ... CONSTRAINED-DELEGATION s4u-client=testuser1@TESTRELM.TEST
Jun 06 06:34:13 ipaserver01.testrelm.test krb5kdc[16265](info): closing down fd 12
Comment 10 errata-xmlrpc 2017-08-01 05:46:16 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2304

Note You need to log in before you can comment on or make changes to this bug.