summaryrefslogtreecommitdiff
path: root/src/providers/ldap/sdap_id_op.c
AgeCommit message (Collapse)AuthorFilesLines
2012-09-05Don't terminate the same connection twiceJakub Hrozek1-6/+0
https://fedorahosted.org/sssd/ticket/1488
2012-08-23Clean up cache on server reinitializationPavel Březina1-0/+38
https://fedorahosted.org/sssd/ticket/734 We successfully detect when the server is reinitialized by testing the new lastUSN value. The maximum USN values are set to zero, but the current cache content remains. This patch removes records that were deleted from the server. It uses the following approach: 1. remove entryUSN attribute from all entries 2. run enumeration 3. remove records that doesn't have entryUSN attribute updated We don't need to do this for sudo rules, they will be refreshed automatically during next smart/full refresh, or when an expired rule is deleted.
2012-08-01Primary server support: support for "disconnecting" connections in LDAPJan Zeleny1-4/+37
This patch adds support for marking existing connections as being disconnected. Each such connection can't be used for new queries and a new one has to be created instead if necessary. This will ensure that pending operations will end gracefully during reconnection. Also all new queries to the server we are reconnecting to will use another (probably newly created) connection.
2012-06-29ldap provider: add sudo usn valuePavel Březina1-0/+1
2012-01-31LDAP: Add enumeration support for servicesStephen Gallagher1-0/+1
2011-11-29Provide means of forcing TLS and GSSAPI enabled/disabled for sdap connectionsJakub Hrozek1-1/+3
2011-05-04Fixed lastUSN checking improvementsJan Zeleny1-2/+2
This patch fixes some issues with setting lastUSN attribute and it adds check against the highest user/group USN after enumeration to keep better track of the real highest USN. Optimal solution here would be to schedule a check of rootDSE entry right after the enumeration finishes, but for the moment this is good enough.
2011-04-19Add last usn checking after reconnectionJan Zeleny1-0/+15
When reconnecting to the LDAP server supporting USNs (either because of new incomming id operation or invokation of callback responsible for checking status of the backend), detect whether the highest USN is lower than the one SSSD has recorded. If so, setup enumeration/cleanup to refresh potentionally changed account information in the SSSD cache. Related ticket: https://fedorahosted.org/sssd/ticket/734
2011-03-14Fix one unlikely case of failure in sdap_id_op moduleJan Zeleny1-1/+3
There can be an unlikely scenario when the first part of sdap_id_op_connect_done works fine and there is no need to mark backend offline. But right after the check, the memory allocation can fail in which case the backend needs to be marked offline along with disabled reconnecting.
2010-12-07ldap: Use USN entries if available.Simo Sorce1-1/+2
Otherwise fallback to the default modifyTimestamp indicator
2010-12-07ldap: add checks to determine if USN features are available.Simo Sorce1-4/+5
2010-12-07ldap: remove variable that was never assigned nor usedSimo Sorce1-8/+0
2010-12-07Pass sdap_id_ctx in sdap_id_op functions.Simo Sorce1-38/+48
2010-09-15Store rootdse supported features in sdap_handlerSumit Bose1-2/+2
2010-07-09Use new LDAP connection framework in IPA dynamic DNS forwarder.eindenbom1-0/+4
2010-07-09Add an interface to try next fail-over server after connection to the active ↵eindenbom1-0/+3
server was unexpectedly dropped.
2010-07-09LDAP connection usage tracking, sharing and failover retry framework.eindenbom1-0/+758