We are using JENKINS since quite some time and have added lots of users over time. Now we are facing a weird problem where the newly added user is showing the group icon left to the name - instance of the single user.
Any idea what this might cause? Did one of you have ever faces such an issue before?
Many thanks in advance, M
It would help if you provide more details about your system. Which Jenkins version are you using, which authorization plugin in which version.
In older versions of Matrix Auth and Role-strategy you could not explicitly specify if you want to add a user or a group.
What message you get for exception e (the output of println(" It is NOT a user, reason: " + e.getMessage()))
I think there are 2 problems here:
- The LDAP security realm is reporting that user1 is not a user but a group
- role-strategy is showing a group icon for what should be a user
For the first problem this might be a configuration issue of the ldap plugin. As I’m not familiar with that plugin I can’t help here.
The second problem can only occur normally when the entry is ambiguous in the config, means you haven’t chosen for an old existing entry if it should reflect a user or a group.
If you add a new entry via the button Add User it should theoretically be impossible that for this user a group symbol is shown.
Note that role-strategy (but also matrix-auth) do call the security realm to check if a user/group exists only to be able to show this in the UI.
If you add a user then only a user with that name will have the corresponding permissions, similar for groups.
The assignment of groups to users is done by the security realm and independent of the auth strategy