-
Notifications
You must be signed in to change notification settings - Fork 47
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
Authentication fails for users not available via libc #2
Comments
👍 This prevent implementing Radius authentication through PAM |
@busbey looks like you started working on this on your fork, could you tell us about it? |
I think I got this working on my fork. I'll see if it's in condition for a PR |
\o/ |
busbey
added a commit
to busbey/libpam4j
that referenced
this issue
May 19, 2015
* Changes PAM.authenticate to return a generic AuthenticatedUser. ** Uses UnixUser.exists instead of manually checking libc.passwd, then returns either a UnixUser or a generic AuthenticatedUser. ** Non-backwards compatible because of the method signature change on PAM.authenticate. * Changes UnixUser to be a subclass of the generic AuthenticatedUser. Fixes kohsuke#2
busbey
added a commit
to busbey/libpam4j
that referenced
this issue
May 19, 2015
* Changes PAM.authenticate to return a generic AuthenticatedUser. ** Uses UnixUser.exists instead of manually checking libc.passwd, then returns either a UnixUser or a generic AuthenticatedUser. ** Non-backwards compatible because of the method signature change on PAM.authenticate. * Changes UnixUser to be a subclass of the generic AuthenticatedUser. Fixes kohsuke#2
there's a pull request on current master. FYI, it's a breaking change because of the API alteration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now users authenticated via PAM are conflated with users local to the box.
Steps to reproduce:
set up a PAM service that authenticates external to the system, ie pam_ldap (but do not make this login)
do not set up a local user with the same name
use libpam4j to authenticate
Ideally, the libc based information should be optional additional info.
The text was updated successfully, but these errors were encountered: