Repository navigation
Replies: 1 comment
|
I tried it also by creating a client in RKI that uses client authenticator It is possible to refer to CKIs JWKS url, but it is not possible to mint an access token that satisfies the respective jwt requirements (see https://www.authlete.com/kb/oauth-and-openid-connect/client-authentication/client-secret-jwt/) to call with e.g. |
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.
In #26502 (comment) I describe a scenario, where multiple keycloak instances (RKI), refer to a cental keycloak instance (CKI) as identity provider.
Now currently, this CKI has to create a client for each of these keycloak instances such that the configuration is possible.
I want to realize the following scenario:
Wouldn't it be enough here to say that the RKIs simply trust tokens minted by CKI to do the token exchange, without requiring a registered client on CKI site?
All reactions