You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SECURITY NOTICE: If you have found a security problem in the UAA, please do not file a public github issue. Instead, please send an email to security@cloudfoundry.org
Thanks for taking the time to file an issue. You'll minimize back and forth and help us help you more effectively by answering all of the following questions as specifically and completely as you can.
What version of UAA are you running?
74.17.0
What output do you see from curl <YOUR_UAA>/info -H'Accept: application/json'?
I have created a client internal-iz-client in an identity zone internal. To generate the token with client_credentials grant_type it works when I add the subdomain in the UAA URL which looks like http://internal.localhost:8080/oauth/token.
What do I want?
I want to pass the identity zone in some other way instead of adding the subdomain to the URL. To be precise, I want to call http://localhost:8080/oauth/token with some additional param or header (or anything else possible) through which it generates the token for the internal-iz-client. How can we do that?
What did you expect to see? What goal are you trying to achieve with the UAA?
I passed X-Identity-Zone-Id in the headers while calling the endpoint to generate the token for this client but it still uses the default Identity-Zone uaa when calling the http://localhost:8080/oauth/token
@swalchemist I have not checked on the latest release but from the documentation it seems to be the same case there as well. The token generation works only when I pass the subdomain but there is no provision to pass the header X-Identity-Zone-Id for generating the token
SECURITY NOTICE: If you have found a security problem in the UAA, please do not file a public github issue. Instead, please send an email to security@cloudfoundry.org
Thanks for taking the time to file an issue. You'll minimize back and forth and help us help you more effectively by answering all of the following questions as specifically and completely as you can.
What version of UAA are you running?
74.17.0
What output do you see from
curl <YOUR_UAA>/info -H'Accept: application/json'
?How are you deploying the UAA?
I am deploying the UAA
What did you do?
internal-iz-client
in an identity zoneinternal
. To generate the token withclient_credentials
grant_type it works when I add the subdomain in the UAA URL which looks likehttp://internal.localhost:8080/oauth/token
.What do I want?
http://localhost:8080/oauth/token
with some additional param or header (or anything else possible) through which it generates the token for theinternal-iz-client
. How can we do that?What did you expect to see? What goal are you trying to achieve with the UAA?
I passed
X-Identity-Zone-Id
in the headers while calling the endpoint to generate the token for this client but it still uses the default Identity-Zoneuaa
when calling thehttp://localhost:8080/oauth/token
What did you see instead?
Please include UAA logs if available.
The text was updated successfully, but these errors were encountered: