Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issuer URL is reported wrong in /.well-known/openid-configuration

See original GitHub issue

What version of UAA are you running?


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:open
  • Created 5 years ago
  • Reactions:3
  • Comments:12 (2 by maintainers)

github_iconTop GitHub Comments

c4milocommented, Oct 8, 2019

@Ianwww, nop. I had to tell my client library to skip discovery and provided the individual URLs to it.

vincentserpoulcommented, Oct 4, 2018

I will also add here the specs of openid itself:

Read more comments on GitHub >

github_iconTop 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 " ...
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 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found