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 #128

Merged
merged 9 commits into from
May 23, 2024

Conversation

giacomini
Copy link
Member

Closes #124

The depth of some fields was not correct for the response obtained
through the REST API, which is the first one tried and the only one that
will survive in the future with VOMS-AA.

In addition, VOMS-AA returns a numeric code for an error condition, not
a string like VOMS server.
* Always process the errors, not only in case an AC has been returned
* For certain errors (user doesn't exist, is suspended, is inactive) do
  not try the legacy endpoint, which doesn't even exist for VOMS AA
* Leave some commented-out debug messages, to be possibly included in
  the output in debug mode (requires some work to propagate the debug
  flag)
Contrary to the VOMS server, VOMS-AA expects that the fqans query
parameter includes also the FQANs specified with the --order command
line argument of voms-proxy-init.
We keep the order query parameter, which is instead expected by the VOMS
server.
And avoid the use of std::next, which is C++11
@giacomini giacomini merged commit 1421b87 into develop May 23, 2024
6 checks passed
@giacomini giacomini deleted the 124-adapt-client-libraries-and-clients-to-voms-aa branch May 23, 2024 12:23
@giacomini giacomini linked an issue May 24, 2024 that may be closed by this pull request
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 this pull request may close these issues.

Adapt client libraries and clients to VOMS-AA
1 participant