UI shows wrong LDAP membership level
Summary
UI shows incorrect project permission level,
Steps to reproduce
-
Have a LDAP user belonging to two different LDAP groups.
-
Create a first Gitlab group with LDAP sync. Sync it with an LDAP group with
Developer
access level. -
Create a second Gitlab group. Sync it with another LDAP group with
Master
access level. -
Create a project as a child of the first Gitlab group.
-
Configure the project to have the second Gitlab group as members.
What is the current bug behavior?
The project shows the user as Developer
on the UI, although it should say Master
, because of the child project configuration.
The user does in fact have Master
permissions, it is just a matter of the UI showing the wrong permissions.
What is the expected correct behavior?
Members should appear as Master
.
We are using 10.8.5-ee