summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSimo Sorce <simo@redhat.com>2012-12-13 18:13:06 -0500
committerJakub Hrozek <jhrozek@redhat.com>2012-12-14 17:26:26 +0100
commit23669fdf7afd1f0b427f98eb20a760101fb80300 (patch)
tree968309975c4410170074b39a98b51f5cf963ebb4
parenteeeae5674c14beced57a45f525db233768959058 (diff)
downloadsssd-23669fdf7afd1f0b427f98eb20a760101fb80300.tar.gz
sssd-23669fdf7afd1f0b427f98eb20a760101fb80300.tar.xz
sssd-23669fdf7afd1f0b427f98eb20a760101fb80300.zip
sssd_pam: Cleanup requests cache on sbus reconect
The pam responder was not properly configured to recover from a backend disconnect. The connections that were in flight before the disconnection were never freed and new requests for the same user would just pile up on top of the now phantom requests. Fixes: https://fedorahosted.org/sssd/ticket/1655
-rw-r--r--src/responder/pam/pamsrv.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/src/responder/pam/pamsrv.c b/src/responder/pam/pamsrv.c
index c94596c4c..4a4d0ce92 100644
--- a/src/responder/pam/pamsrv.c
+++ b/src/responder/pam/pamsrv.c
@@ -91,7 +91,10 @@ static void pam_dp_reconnect_init(struct sbus_connection *conn, int status, void
DATA_PROVIDER_VERSION,
"PAM");
/* all fine */
- if (ret == EOK) return;
+ if (ret == EOK) {
+ handle_requests_after_reconnect(be_conn->rctx);
+ return;
+ }
}
/* Handle failure */