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

Introduce support for Authentication profiles in Argus #21

Open
andreaceccanti opened this Issue Apr 12, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@andreaceccanti
Copy link
Member

andreaceccanti commented Apr 12, 2017

This issue tracks the development of authentication profiles support in Argus.
The topic has been widely discussed among the Argus collaboration, three proposals have been written, which are now collected here. Consensus was reached on proposal 3.

Proposal 3 summary

We propose to define an additional PIP, running in the Argus PEP daemon, that has the responsibility of understanding the LoA of the user certificate in the authorization request and
remove the certificate-related attributes (i.e., subject, subject-issuer, vo, fqan and pfqan and EMI profile equivalents) if the LoA of the user certificate in the authorization request is not allowed by the local authentication profile policy (which will then result in a NotApplicable authorization decision).

We will use the VO-CA-AP policy syntax to define which LoAs are allowed for which VOs and for certificates without VOMS extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment