-
Notifications
You must be signed in to change notification settings - Fork 38
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
Domain Login overrides LDAP login #70
Comments
use |
Yes that works... but my user base is pretty non-technical, so it will also cause a lot of problems. Nobody thinks to type .\ before their username, and even if I post signs and details, only half of my users will read them... |
I can possible add another setting to reverse this behavior. |
That would be great... thanks. |
- #70 If a system is a domain member pgina will authenticate users by def. against the domain To invert this behavior an admin can set PreferLocalAuthentication (if .\username is not convenient). pGina will than authenicate against the local machine (a pGina authentication is always local) To authenticate against the domain a user than needs to pass the domainname, like domain\user or user@domain.local
thanks! I will give it a try. |
The new option works perfectly for us, thanks! |
Thanks for your work with pgina fork...
I am trying to setup a computer lab on a university campus. The computer lab will use the LDAP plugin to authenticate students against the university servers... (this works)
I also have the computers on our local active directory, so I can push configuration changes centrally...
The problem is that users in the active directory cant sign into the computers via LDAP. It seems if the user has an account in our active directory, pgina fork will not check the LDAP credentials, even if the active directory credentials fail...
Is there a way to prevent pgina from trying to authenticate the user against our active directory? Ideally I would only authenticate local accounts (for admin access) and LDAP users...
Thanks!
The text was updated successfully, but these errors were encountered: