diff options
| author | Jakub Hrozek <jhrozek@redhat.com> | 2015-09-21 15:53:50 +0200 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2015-09-23 09:45:57 +0200 |
| commit | 3366a3cdbf93eea757123e11a32307a005c05443 (patch) | |
| tree | daa33ad0cfa14def3e9989239405bd171b0e80aa /src/util/io.c | |
| parent | c40b2e130b559caf90cf737977edba1f5703efc9 (diff) | |
| download | sssd-3366a3cdbf93eea757123e11a32307a005c05443.tar.gz sssd-3366a3cdbf93eea757123e11a32307a005c05443.tar.xz sssd-3366a3cdbf93eea757123e11a32307a005c05443.zip | |
IPA: Only re-fetch the keytab if modifyTimestamp is newer than last LDAP connection
Resolves:
https://fedorahosted.org/sssd/ticket/2639
When a subdomain account lookup errors out, try to re-setup the trust
object. Only do this, if the connection was established after the last
re-set of the trust object.
Internally, the setup function looks at the modifyTimestamp operational
attribute of the TDO. If the modifyTimestamp is newer than the last
keytab check, then the trust was re-created and we need to fetch the
keytab again.
Marking the back end as online re-sets the TDO check timestamp so that
after cycling the sssd, the keytab would always be checked.
Diffstat (limited to 'src/util/io.c')
0 files changed, 0 insertions, 0 deletions