LDAP Users Have Been Successfully Authenticated but No ROLES Have Been Assigned
Problem
LDAP Configuration
Login Error
Also note that <MANTA_SERVER_HOME>/logs/manta-dataflow.log
shows that the user demouser4 has been successfully authenticated but no ROLES have been assigned to the user.
Request from host '0:0:0:0:0:0:0:1' (direct origin |
Root Cause
This happens when the user associated with the group that is used in the group search base and group search filter from the LDAP configuration in Manta Admin UI is not fully qualified with a unique DN.
In this case, the group demogroup4 has memberUid=demo4user but demouser4 is not fully qualified with its full DN.
Resolution
When configuring the group search filter, ensure that the entities representing users in that group are fully qualified with a full DN instead of just the cn entry.
For example, the user demouser3 is defined as memberUid attribute in membergroup3 and has a fully qualified DN
memberUid: uid=demouser3,ou=Users,ou=getmanta,dc=maxcrc,dc=com.
When the user demouser3 logs in to Manta dataflow viewer, the user is not only authenticated but also authorized and the appropriate ROLES are assigned to the user.
Also note that <MANTA_SERVER_HOME>/logs/manta-dataflow.log
now shows the user demouser3 as successfully authenticated and the appropriate ROLES have been assigned.
Request from host '0:0:0:0:0:0:0:1' (direct origin |
Conclusion
When using LDAP, there are two ways groups can be created, using Group or Group of Unique Names.
It is recommended that the groups be created using Group of Unique Names, as this entry automatically registers each unique user under the uniqueMember attribute while Group only has the memberUid attribute, and its value may not necessarily be unique.
Group of unique names:
Group:
If Group has to be used to configure LDAP in Manta Admin UI, then the memberUid attribute has to be manually edited to fully qualify the user DN.