-
Notifications
You must be signed in to change notification settings - Fork 911
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
Allow hybrid LDAP + properties file group authentication #608
Comments
👍 This would be an extremely useful feature |
Yes please. We would require this ability because we do not have an LDAP autogroup for everyone in our company. Also, just the option to use LDAP as authentication without roles would be helpful. |
Have updated the hybrid-login module for rundeck 2.0.x... Works fine for me. In case of you'll find it here: |
I’m going to try it out today. From: Pierre Hanselmann [mailto:notifications@github.com] Have updated the hybrid-login module for rundeck 2.0.x... Works fine for me. In case of you'll find it here: — |
Looks like its authenticating correctly using LDAP but I’m still facing the !role issue because now every users must have a role. That’s still a problem for us as we do not define roles in LDAP for each user. Thanks, From: Pierre Hanselmann [mailto:notifications@github.com] Have updated the hybrid-login module for rundeck 2.0.x... Works fine for me. In case of you'll find it here: — |
Hey Greg any news on this one? I'm looking for a more "standard" way to do it (Seems you've implmented that for PAM). Why i'm not able to use something like this (looks like roles are totally ignored): MyLoginModule {
}; Auth works but role assignment seems not processed: And i get the !Role exception message.... Any feedback? |
The |
Don't be sorry you're doing an awsome job! Thanks for the update. |
Could you add this feature? There's a good example here:
https://github.com/coiouhkc/rundeck-hybrid-login
The idea is to have a LDAP authentication and map user roles based on properties file. The above example is case sensitive which should be case insensitive.
Thanks,
Pierre
The text was updated successfully, but these errors were encountered: