#3043 proxy provider loops when sss is in proxy_pam_target
Closed: wontfix 4 years ago by pbrezina. Opened 7 years ago by pbrezina.

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.


Not really important to fix unless someone complains.

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => todo

Metadata Update from @pbrezina:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

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.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4076

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata