Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proxy provider loops when sss is in proxy_pam_target #4076

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

proxy provider loops when sss is in proxy_pam_target #4076

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3043

  • Created at 2016-06-13 13:34:04 by pbrezina
  • Closed at 2020-03-24 14:16:41 as wontfix
  • Assigned to nobody

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:

  • Issue set to the milestone: SSSD Patches welcome

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:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant