feature test: JWT bearer across zones #3348
Merged
+348
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I think it was simply forgotten to allow it, but in documentation there is response_type with "token id_token", but the flow is not allowed to return it. Fix this
The test uses 3 zones in UAA to represent 3 identity zones. This PR needs #3344 because jwt bearer should / must return an id_token if the client is configured with openid, similar to password grant.
fhanik
approved these changes
Mar 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The test uses 3 zones in UAA to represent
3 identity organizations.
UAA zone with marisaa is the Issuer treated as Trusted Corporate Token
Testzone3 is the proxy which trusts UAA zone.
Testzone4 is the consumer organisation, which trusts testzone3.
This PR needs #3344
because jwt bearer should / must return an id_token if the client is configured with openid, similar to password grant.
After #3309
The test can be finalized so that a token from UAA zone can be conumed in testzone4 which has not direct trust to UAA zone.
The login_hint in request signalize the IdP that token is not from testzone3 but testzone3 should validate it first after that testzone3 can create an assertion for testzone4