Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Personal certificates with "sn" and "gn" fields not supported #6599

Open
fstagni opened this issue Dec 1, 2022 · 0 comments
Open

Personal certificates with "sn" and "gn" fields not supported #6599

fstagni opened this issue Dec 1, 2022 · 0 comments
Assignees
Milestone

Comments

@fstagni
Copy link
Contributor

fstagni commented Dec 1, 2022

Dear all,

We have an issue with certificates having "sn" and "gn" fields, as in the example below:

/C=DE/O=GridGermany/OU=Max-Planck-Gesellschaft/OU=Max-Planck-Institut fuer Kernphysik/sn=Werner/gn=Felix/CN=Felix Werner

When users issue a proxy with dirac-proxy-init they get:

DN /C=DE/O=GridGermany/OU=Max-Planck-Gesellschaft/OU=Max-Planck-Institut fuer Kernphysik/SN=Werner/GN=Felix/CN=Felix Werner is not registered

I tried to manually change lower case letters to upper case:

/sn=Werner/gn=Felix/ -> /SN=Werner/GN=Felix/

in the CS and it seems to work fine. However, the VOMS2CSAgent then updates again the CS with lower case letters and users cannot issue a proxy anymore.

Is there some fix needed in dirac-proxy-init or in some other component to handle this use case?

Thank you,

Luisa

Originally posted by @arrabito in #6437

--> update VOMS2CSAgent

@fstagni fstagni added this to the v8.0 milestone Dec 1, 2022
@fstagni fstagni self-assigned this Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant