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

scopes_supported in the authorization server wk is not used #136

Open
matteo-cristino opened this issue Jul 15, 2024 · 2 comments
Open

scopes_supported in the authorization server wk is not used #136

matteo-cristino opened this issue Jul 15, 2024 · 2 comments

Comments

@matteo-cristino
Copy link
Collaborator

As you can see in #135 I added placeholder for some mutable informations, but during tests I never substitute the scopes_supported placeholder and test works fine.

Is it correct that this field is not used during all the flow?

@puria
Copy link
Member

puria commented Jul 16, 2024

who knows 🤔

@matteo-cristino
Copy link
Collaborator Author

Looking at this seems that the scopes_supported is only reccomended and that the user can request a specific scope in the authorization and/or token call.

We are not using it since in our case the user specify the credential he/she want to obtain in the /par call with

{
  "authorization_details": [
    {
      "credential_configuration_id": "discount_from_voucher",
      "locations": [
        "https://issuer1.zenswarm.forkbomb.eu/credential_issuer"
      ],
     "type": "openid_credential"
    }
  ],
  "everything": "else"
}

And in the next calls this is retrieved internally from the authorization server cache.

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

2 participants