Issuer URL is reported wrong in /.well-known/openid-configuration
See original GitHub issueIssue Description
What version of UAA are you running?
4.11.0
How are you deploying the UAA?
I am deploying the UAA
- locally only using gradlew
What did you do?
curl http://localhost:8080/uaa/.well-known/openid-configuration | jq .
What did you expect to see? What goal are you trying to achieve with the UAA?
I expect to see issuer with value http://localhost:8080/uaa since that’s what I have set in my uaa.yml
file
What did you see instead?
It wrongly returns http://localhost:8080/uaa/oauth/token as issuer
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Issuer metadata missing when adding a new OIDC connection
It seems that the metadata in this case is reporting that an “id_token” response is available even though the client is missing a...
Read more >Ask Question - Stack Overflow
Unable to resolve the OpenID Configuration with the provided Issuer of "https://login.microsoftonline.com/xxxxx/.well-known/openid-configuration ...
Read more >SSL certificate problem when fetching OIDC metadata
This URL is protected by a certificate signed by COMODO. Now when an authentication starts, I receive the following error in the logs:....
Read more >OpenID redirect failed. Validation error: unexpected issuer URI
I put https://cas.ucdavis.edu/cas/oidc in for the issuer URL, ... concatenating the string /.well-known/openid-configuration to the Issuer.
Read more >JWT::InvalidIssuerError on Decode JWT (OpenID Connect)
I already contacted Support and they said that basically the error was from Discourse (Which I don't think so).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Ianwww, nop. I had to tell my client library to skip discovery and provided the individual URLs to it.
I will also add here the specs of openid itself: https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig