Skip to content

VOMS2CSAgent: support of IAM nested groups #8487

@arrabito

Description

@arrabito

In CTAO we are defining IAM groups with the following structure:

       ctao.dpps.test/dpps/user
       ctao.dpps.test/dpps/pipelines
       ctao.dpps.testdpps/pipelines/user
       ctao.dpps.test/dpps/pipelines/manager
       ctao.dpps.test/dpps/dataquality/user

etc.

However this nested structure doesn't seem to be supported by the VOMS2CSAgent, see the log below:

2026-03-20T17:24:51,868663Z Configuration/VOMS2CSAgent/VOMS2CSSynchronizer [139646936368960] DEBUG: {'/CN=DPPS User': {'CA': '/CN=DPPS Development CA', 'nickname': 'test-user', 'certSuspended': False, 'suspended': False, 'mail': 'dpps@test.example', 'Roles': ['/ctao.dpps.test/Role=dpps/Role=pipelines/Role=user', '/ctao.dpps.test/Role=dpps/Role=user', '/ctao.dpps.test/Role=dpps/Role=dataquality/Role=user', '/ctao.dpps.test', '/ctao.dpps.test/Role=dpps/Role=archive/Role=user']}}

Do you think that we could modify the VOMS2CSAgent behaviour to support this structure?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions