Repository navigation
Replies: 1 comment
|
Context here: #27961 (reply in thread) |
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.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
we are using a vendor product that relies on keycloak for its operation. We operate an internal OIDC IDP that we have set up with keycloak to broker human use-cases for our vendor product. This works as expected.
We would also like to enable the ability for keycloak to validate JWT's issued by our OIDC IDP for api access.
Meaning, we want an access token fetched from our external IDP to be correctly validated by keycloak. We don't need keycloak to be able to issue any tokens, simply accept the ones from our IDP.
I have found this stackoverflow thread: https://stackoverflow.com/questions/75765714/error-invalid-jwt-token-while-setting-up-keycloak-external-idpoidc and followed the instructions.
Step 6. was a bit confusing to me as i am not entirely sure what exactly needed to be done.
When fetching
curl https://{KEYCLOAK_URL}/auth/realms/{REALM}/protocol/openid-connect/certsthe jwks of our remote idp does not show up.I know it seems like i can configure something under
Realm settings -> Keys, but I would have thought they would be added once I enabledUse JWKS url.Is there something missing from the steps outlined in the stackoverflow thread? Or am i fundamentally misunderstanding something, that this scenario is not available with keycloak. One reason why i am doubting this may work at all, is due to the issuer of the
access_tokennot being keycloak itself and keycloak's issuer is set to itselfhttps://{KEYCLOAK_URL}/auth/realms/{REALM}/.well-known/openid-configuration.All reactions