summaryrefslogtreecommitdiffstats
path: root/server/responder/pam/pamsrv_cache.c
Commit message (Collapse)AuthorAgeFilesLines
* Add support for offline auth cache timeoutStephen Gallagher2009-10-221-2/+18
| | | | | | | | | This adds a new option (offline_credentials_expiration) to the [PAM] section of the sssd.conf If the user does not perform an online authentication within the timeout (in days), they will be denied auth once the timeout passes.
* Revert "Use syslog for logging error conditions in SSSD"Stephen Gallagher2009-09-231-1/+1
| | | | | | | | This reverts commit 8c50bd085c0efe5fde354deee2c8118887aae29d. Amended: commit 1016af2b1b97ad4290ccce8fa462cc7e3c191b2e also made use of the SYSLOG_ERROR() macro, so those portions of that code also needed to be reverted.
* Use syslog for logging error conditions in SSSDJakub Hrozek2009-09-211-1/+1
| | | | | This is just a band-aid until ELAPI is fully functional and ready to use.
* Split database in multiple filesSimo Sorce2009-09-081-1/+8
| | | | | The special persistent local database retains the original name. All other backends now have their own cache-NAME.ldb file.
* Rename sysdb_req to sysdb_handle.Simo Sorce2009-07-031-6/+0
| | | | | | | | | This sysdb_req has always really been a transaction handle and not a request. This is part of a set of patches to rewrite transaction support in sysdb to a hopefully better API, that will also let use use tevent_req async style to manipulate our cache.
* Move actual password caching into sysdbSimo Sorce2009-05-181-111/+1
| | | | Convert auth modules to do the caching themselves
* Fix crypt functions to not use static buffers.Simo Sorce2009-05-181-9/+7
| | | | Also fix style, clarify, and simplify some logic.
* Use different attribute for cached passwords change timeSumit Bose2009-04-281-2/+2
|
* Use different attribute for cached passwordsSimo Sorce2009-04-271-3/+3
| | | | | | | This fixes a bug with legacy backends where the cached password would be cleared on a user update. Using a different attribute we make sure a userPassword coming from the remote backend does not interfere with a cachedPassword (and vice versa).
* Implement credentials caching in pam responder.Simo Sorce2009-04-131-0/+275
Implement credentials caching in pam responder. Currently works only for the proxy backend. Also cleanup pam responder code and mode common code in data provider. (the data provider should never include responder private headers)