summaryrefslogtreecommitdiffstats
path: root/src/python/pysss.c
diff options
context:
space:
mode:
authorFabiano FidĂȘncio <fidencio@redhat.com>2017-02-02 13:06:30 +0100
committerJakub Hrozek <jhrozek@redhat.com>2017-03-03 13:54:14 +0100
commit189db5329db0277425bb3bdd785c19aee23bb364 (patch)
tree52b59fb950f2ef844e878054252362944ab6d1d2 /src/python/pysss.c
parent8718ff9ccd29f6431bfa8630bfa3576b2692c9ee (diff)
downloadsssd-189db5329db0277425bb3bdd785c19aee23bb364.tar.gz
sssd-189db5329db0277425bb3bdd785c19aee23bb364.tar.xz
sssd-189db5329db0277425bb3bdd785c19aee23bb364.zip
CACHE_REQ: Add cache_req_data_set_bypass_cache()
This new cache_req_data method has been added because of the upcoming changes in the PAM responder. For deciding whether to contact the cache, or just query the data provider directly, PAM responder calls pam_initgr_check_timeout() which will return whether the cache entry may still be valid. The cache will be contacted only in case the cache entry is still valid, otherwise the data provider will be called. pam_initgr_check_timeout() basically checks whether the user (being looked up) is still a part of an in-memory hash table. Because the entry is a part of the hash table for really short period of time, and is automatically removed, the communication with the data provider is forced to happen quite often. As the follow-up changes should not modify this behaviour, this function was introduced so we can still call pam_initgr_check_timeout() and pass its result to the cache_req call that will perform the lookup. Related: https://fedorahosted.org/sssd/ticket/1126 Signed-off-by: Fabiano FidĂȘncio <fidencio@redhat.com> Reviewed-by: Sumit Bose <sbose@redhat.com> Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
Diffstat (limited to 'src/python/pysss.c')
0 files changed, 0 insertions, 0 deletions