cloudfoundry / cloudfoundry/uaa
Using a hostname within the uaa.url causes misconfiguration of oidc .well-known endpoint.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 844
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 27
Description
When setting the uaa.url to "https://172.31.75.4:8443", the OIDC .well-known endpoint produces a valid endpoint list with 8443 as part of each url (i.e. authorize, token, userinfo, etc). When uaa.url is specified using a hostname like "https://www.example.com:8443", the .well-known endpoint does not produce valid OIDC endpoints. For each, the hostname is present without the port number. My instinct is the uaa.url should not contain the port number and simply use the uaa.ssl.port concatenated to the uaa.url? Not sure on this part. Simply thinking out loud.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the OIDC .well-known response with uaa.url set to an IP address and then to a hostname, both using port 8443. Inspect how the endpoint constructs the authorize, token, and userinfo URLs; done means hostname-based configuration produces valid endpoints with the intended port consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100