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

Adapt client libraries and clients to VOMS-AA #124

Closed
giacomini opened this issue Mar 27, 2024 · 3 comments · Fixed by #128
Closed

Adapt client libraries and clients to VOMS-AA #124

giacomini opened this issue Mar 27, 2024 · 3 comments · Fixed by #128
Assignees

Comments

@giacomini
Copy link
Member

VOMS-AA is the VOMS endpoint of INDIGO-IAM

@giacomini giacomini self-assigned this Apr 2, 2024
@bbockelm
Copy link
Contributor

@giacomini - what's the current plans / timelines on this? Particularly, is a new client going to be available prior to the shutdown of the WLCG VOMS-Admin instances?

@giacomini
Copy link
Member Author

Yes. I've opened a PR with the current work, which I'd like to merge next week. Feel free to review.

@giacomini
Copy link
Member Author

The option -order doesn't work for voms-proxy-init. This is because the request to the server is something like GET /generate-ac?fqans=/test.vo&lifetime=43200&order=/test.vo/G1, but VOMS-AA uses only the fqans list. In fact, the java version sends GET /generate-ac?fqans=/test.vo/G1&lifetime=43200, which apparently is processed correctly also by the VOMS server.

@giacomini giacomini linked a pull request May 24, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants