You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a glitch in when proxy provider (or SSS_PAM_AUTHENTICATE request to be more precise) starts looping if sss is defined in proxy_pam_target pam stack and invalid password is provided during authentication. The pam child is never finished and eventually it is killed by timeout, however the requests keep going indefinitely.
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3043
There's a glitch in when proxy provider (or SSS_PAM_AUTHENTICATE request to be more precise) starts looping if sss is defined in proxy_pam_target pam stack and invalid password is provided during authentication. The pam child is never finished and eventually it is killed by timeout, however the requests keep going indefinitely.
Comments
Comment from jhrozek at 2016-06-16 21:48:11
Not really important to fix unless someone complains.
milestone: NEEDS_TRIAGE => SSSD Deferred
Comment from jhrozek at 2016-07-13 13:54:19
Fields changed
rhbz: => todo
Comment from pbrezina at 2017-02-24 14:46:59
Metadata Update from @pbrezina:
Comment from pbrezina at 2020-03-24 14:16:40
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Comment from pbrezina at 2020-03-24 14:16:42
Metadata Update from @pbrezina:
The text was updated successfully, but these errors were encountered: