We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I may be missing a section in the specification that discusses ordering dependencies, but my reading of https://openid.net/specs/openid-connect-basic-1_0.html#Scopes is that the order of the tokens in the "scope" parameter don't matter.
Right now the mockoidc server requires that "openid" be the first token in the scope list before it will add id_token.
If the spec doesn't require ordering, would it be appropriate to change the logic to iterate over the scopes?
See pull request #48
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I may be missing a section in the specification that discusses ordering dependencies, but my reading of https://openid.net/specs/openid-connect-basic-1_0.html#Scopes is that the order of the tokens in the "scope" parameter don't matter.
Right now the mockoidc server requires that "openid" be the first token in the scope list before it will add id_token.
If the spec doesn't require ordering, would it be appropriate to change the logic to iterate over the scopes?
See pull request #48
The text was updated successfully, but these errors were encountered: