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

PBIS: domain-join Utility Creates Wrong Stack-Order When pam_faillock Present #23

Closed
ferricoxide opened this issue Nov 12, 2015 · 0 comments

Comments

@ferricoxide
Copy link
Member

The pbis.sls leverages the PBIS domainjoin-cli utility to do the heavy-lifting surrounding joining the client to the domain. However, the domainjoin-cli utility (through at least PBIS 8.3.0) defaults to inserting pam_lsass modules late in the /etc/pam.d/password-auth stack. When the pam_faillock modules are present ahead of the pam_lsass modules and a PBIS user attempts to perform password-based authentication, the pam_faillock modules abort the PAM-call before the pam_lsass modules may be referenced. This results in PBIS users only being able to do non-PAM authentications (SSH key, GSSAPI tokens, etc.)

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