You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configured to use GSSAPI Kerberos encryption, the LDAP provider requests a ticket for 300 seconds. When this time is up, the next time the LDAP provider attempts to make a request to the remote server, it is refused, receiving the error "Cannot contact LDAP server". This causes the request to fail and the domain to enter offline mode.
As discussed on IRC, when we receive this error, we should check whether our kerberos ticket is expired. If it is, we should kinit and retry before going offline.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/299
When configured to use GSSAPI Kerberos encryption, the LDAP provider requests a ticket for 300 seconds. When this time is up, the next time the LDAP provider attempts to make a request to the remote server, it is refused, receiving the error "Cannot contact LDAP server". This causes the request to fail and the domain to enter offline mode.
As discussed on IRC, when we receive this error, we should check whether our kerberos ticket is expired. If it is, we should kinit and retry before going offline.
Comments
Comment from sgallagh at 2009-12-09 06:00:44
Fixed by d239b49
fixedin: => 1.0.0
resolution: => fixed
status: new => closed
Comment from dpal at 2012-01-19 02:28:57
Fields changed
rhbz: => 0
Comment from sgallagh at 2017-02-24 14:43:06
Metadata Update from @sgallagh:
The text was updated successfully, but these errors were encountered: