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

Review mixing capability-based and group-based AuthZ in a single token #4

Open
msalle opened this issue Dec 20, 2023 · 0 comments
Open

Comments

@msalle
Copy link
Contributor

msalle commented Dec 20, 2023

Relevant for WLCG and AARC, but I think we should decide not to have capability-based and group-based AuthZ mixed in a single token. When there is a need for both (perhaps don't know what the audience understands) two separate should be sent.

This is not the same as adding a VO to a capability-based token which would be used for e.g. accounting or setting the context (namespace).

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