Replies: 1 comment
-
|
#14823 seems related to this problem |
Beta Was this translation helpful? Give feedback.
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,
we use Keycloak as IDP for our APIs and I want to get rid of the static username & password login flows used for testing in CI pipelines. My idea is to use the tokens provided by CircleCI or GitHub in order to exchange those for a JWT from our Keycloak with suitable roles set to run a test.
It seems to me like Keycloak Token Exchange - external to internal should be able to solve this, but I can't add the CircleCI IDP to Keycloak.
My problem is in the "Add OpenID Connect v1.0 provider" screen:

CircleCI provides only an issuer and
jwks_uribut not an authorization or token URL and it also doesn't require client ID or secret.The
.well-known/openid-configurationof the CircleCI IDP looks like this:{ "claims_supported": [ "aud", "sub", "iss", "iat", "exp", "oidc.circleci.com/project-id", "oidc.circleci.com/context-ids", "oidc.circleci.com/vcs-ref", "oidc.circleci.com/vcs-origin" ], "id_token_signing_alg_values_supported": [ "RS256" ], "issuer": "https://oidc.circleci.com/org/OUR-ACCOUNT-UUID", "jwks_uri": "https://oidc.circleci.com/org/OUR-ACCOUNT-UUID/.well-known/jwks-pub.json", "request_uri_parameter_supported": false, "response_types_supported": [ "id_token" ], "scopes_supported": [ "openid" ], "service_documentation": "https://circleci.com/docs/2.0/openid-connect-tokens/", "subject_types_supported": [ "public", "pairwise" ] }So my questions are:
Beta Was this translation helpful? Give feedback.
All reactions