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

locations and resource parameters requirements #378

Open
babisRoutis opened this issue Aug 21, 2024 · 0 comments
Open

locations and resource parameters requirements #378

babisRoutis opened this issue Aug 21, 2024 · 0 comments

Comments

@babisRoutis
Copy link
Contributor

resource
Currently, spec recommends to use the resource parameter when placing a authorization request (PAR or not), when
a) scope is being used &
b) > If the Credential Issuer metadata contains an authorization_servers property,

locations
Similarly, spec requires to include it in the authorization_details again when authorization_servers is present.

To my understanding both of those parameters make sense when the credential issuer is not acting an authorization server.

Given that nothing prevents an issuer (which acts also as an authorization server) from populating the authorization_servers with its own - single - issuer id, I think that the requirements could be better expressed by simply stating that
resource is recommended and locations is required only when credential issuer is not acting as an authorization server and remove the reference to the authorization_servers attribute.

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