You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFL currently defines user DN as the concatenation of the user name attribute, the login and the users base. This notably prevents from finding a user in a subtree of the users base (see rackslab/Slurm-web#447) or authenticating when the DN does not contain the user name (see rackslab/Slurm-web#446).
RFL should actually lookup the DN of the user, providing the user name attribute and its login in the subtree scope, and then try to authenticate using this DN.
The text was updated successfully, but these errors were encountered:
Add posibility to lookup user DN in the scope user base subtree before
trying authentication instead of expecting the DN is the simple
concatenation of the user name attribute, the login and the user base.
This feature can be enabled with LDAPAuthentifier(lookup_user_dn=True).
fix#30
RFL currently defines user DN as the concatenation of the user name attribute, the login and the users base. This notably prevents from finding a user in a subtree of the users base (see rackslab/Slurm-web#447) or authenticating when the DN does not contain the user name (see rackslab/Slurm-web#446).
RFL should actually lookup the DN of the user, providing the user name attribute and its login in the subtree scope, and then try to authenticate using this DN.
The text was updated successfully, but these errors were encountered: