Explain omitted Group Members after a GroupSync

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Description

Once a LDAP GroupSync has been run, messages are issued in the logs to mention which users need to log in to gain access:

User with DN `uid=john0,ou=people,dc=example,dc=com` should have access
to 'my_group' group but there is no user in GitLab with that
identity. Membership will be updated once the user signs in for
the first time.

There is no other mention in the UI of why some members of the LDAP group aren't listed on the Group's Members page. There should be some sort of UI cue as to why this is. Admins that don't have access to the logs should be able to see this explanation.

Proposal

In the Group's Members page, consider one of the following messages for Owners (and maybe Masters?):

  • Acknowledge that x number of members may not be visible because they need to login
  • Mention, in general, that members will be visible once they login
  • Mention the dns of members who need to login.

I don't like mentioning the dn in the UI so I like the first two options better, but leave it for discussion.

Links / references

Mentioned in ticket: https://gitlab.zendesk.com/agent/tickets/70018

Edited Jun 26, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading