Repository navigation
Replies: 1 comment
|
I'm looking to support this scenario too. It seems that token-exchange was supported in Token Exchange V1. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
The new Token Exchange V2 removed Public Clients support saying;
That's not exactly true.
We use public clients for external IDPs tokens token exchange.
Scenario:
REST API protected by the Keycloak
USER has "other" IDPs token which is the Keycloak linked to as an external provider.
USER has no idea which provider the REST API is secured with, but can get this information via OpenAPI or OAuth 2.0 Protected Resource Metadata.
USER has no "client_secret" and use public client to exchange it's token to the Keycloak's one.
KEYCLOAK must validate the audience to accept only those external IDP tokens that are issued specifically for it.
Is there something wrong with this scenario?
Best,
Dmitry
All reactions