-
Notifications
You must be signed in to change notification settings - Fork 122
fix(gateway): Fix ldap binding for setups where users can't read thei… #593
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
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
Tested successfully to work with an ACL for users to read their own groups and without it (when using bind credentials). |
|
Hello @Cornelicorn and @behrmann, thank you very much for your contribution 👍 I'll give it a look with rackslab/RFL#54 ASAP. |
15bd529 to
ebe9aff
Compare
|
Squashed the typo into the first commit |
rezib
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
I have to release a new version of RFL with rackslab/RFL#54 landed before merging this. |
4128eed to
1703803
Compare
After successful user authentication, when service bind dn and password are defined in configuration, Slurm-web now retrieves user information and user groups in LDAP with these credentials by default. This solves issues where Slurm-web is unable to retrieve user groups when users do not have read permissions in groups branch of LDAP directory. When service bind dn and password are not defined in configuration, Slurm-web keeps using authenticated user permissions lookup user information and user groups. The previous behavior can be restored by setting lookup_as_user = yes under the [ldap] section in gateway configuration file. fix rackslab#587
This is required to get LDAPAuthentifier() lookup_as_user argument.
…r own groups
Closes #587
Depends on rackslab/RFL#54