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
UAA acts as OAuth2 authorization server and OIDC one. For OIDC we publish well-knonw -> UAA/.well-known/openid-configuration
But UAA should also publish "/.well-known/oauth-authorization-server"
https://datatracker.ietf.org/doc/html/rfc8414
The text was updated successfully, but these errors were encountered:
@Kehrlann FYI , wdyt ?
Sorry, something went wrong.
@strehle Unless our customers require it, I don't think this is high priority:
Since we already have oidc, it should be good enough in most use-cases.
No branches or pull requests
UAA acts as OAuth2 authorization server and OIDC one.
For OIDC we publish well-knonw -> UAA/.well-known/openid-configuration
But UAA should also publish "/.well-known/oauth-authorization-server"
https://datatracker.ietf.org/doc/html/rfc8414
The text was updated successfully, but these errors were encountered: