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:45:19 +0100
commitdd1d16b055ef8091aa77fd656b79b9c581c71ff4 (patch)
tree5abc2c7b7db59dddf66552e231c20e9efb209855
parent096119e8f0d9388c1c837c093ced61eec76057c8 (diff)
downloadsssd-dd1d16b055ef8091aa77fd656b79b9c581c71ff4.tar.gz
sssd-dd1d16b055ef8091aa77fd656b79b9c581c71ff4.tar.xz
sssd-dd1d16b055ef8091aa77fd656b79b9c581c71ff4.zip
sssd_pam: Cleanup requests cache on sbus reconect1.9.2-45
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 */