Improve IAMService user to CS conversion#8491
Improve IAMService user to CS conversion#8491maxnoe wants to merge 1 commit intoDIRACGrid:integrationfrom
Conversation
2d5e13c to
b1fbfd8
Compare
|
@chaen the CI failure here seems unrelated to me |
|
@maxnoe is that ready to be reviewed now? |
|
I would be happy about a review, yes, but I left it on draft as I also wanted to test it in our integration test environment but didn't have a chance yet. |
|
I've just tried it against our prod server, and I see discrepencies, but I did not yet dig down in it |
There is an additional filter now to only create entries for groups that are actually voms roles. I would expect that you now get less roles attached to users, but the roles that are no longer attached do not correspond to real voms roles in the iam server. |
|
There's definitely something off with the logic as it starts adding people without a single |
ok, thanks, I will dig into that next week |
Where should this filtering happen? The Should |
0bffc2e to
9d725c9
Compare
|
oos sorry I pushed by mistake, I'll fix my mess |
73737a6 to
9d725c9
Compare
- Handle nested groups - Filter groups by vo name - Filter groups by having voms.role label - Add tests
7c8f92c to
159b51e
Compare
|
I finally ran this in our test setup with groups mapped to the nested group voms roles. One observation: the voms2cs script did not modify groups that didn't yet have any users. I needed to add an initial I'm also a bit confused about the "Multi-DN" users. As far as I can see, there is a one-to-one mapping of users and dns here. |
|
I think this might be because I messed up the certificate creation for the two test users, the dn is |
|
Confirmed: with correct |
BEGINRELEASENOTES
*Core
FIX: Improve VOMS2CSAgent to handle nested groups and only sync groups that have the voms.role label
ENDRELEASENOTES
Closes #8487