Conversation
jfhcagip
force-pushed
the
fixCNUseInRolebindings
branch
from
d33c69b to
eace6c4
Compare
jfhcagip
force-pushed
the
fixCNUseInRolebindings
branch
from
eace6c4 to
5fca7c1
Compare
jfhcagip
added a commit
that referenced
this pull request
Mar 24, 2026
When creating rolebindings, kubi uses the full DN (Ex: CN=GROUP_CN, OU=SOME_OU_1,OU=SOME_OU_2,OU=SOME_OU_13,OU=SOME_OU_4) of the transversal groups instead of the CN (GROUP_CN). This PR fixes this issue, without it, a user would be linked to a group cn on login, but inside the cluster, the rolebinding would be on the group dn, which would effectively not give the expected rights to the user
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When creating rolebindings, kubi uses the full DN (Ex: CN=GROUP_CN, OU=SOME_OU_1,OU=SOME_OU_2,OU=SOME_OU_13,OU=SOME_OU_4) of the transversal groups instead of the CN (GROUP_CN).
This PR fixes this issue, without it, a user would be linked to a group cn on login, but inside the cluster, the rolebinding would be on the group dn, which would effectively not give the expected rights to the user