Repository navigation
Client authentication x509 for external identity provider #38265
Unanswered
PoissonFraise
asked this question in
Q&A
Replies: 1 comment 3 replies
|
Keycloak brokering to an external IDP using If the external IDP doesn't support this you can attempt to do the following. Leave the client authentication as using client secret with any random value. Globally configure mTLS for outgoing HTTP requests. See https://www.keycloak.org/server/outgoinghttp using |
3 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,
I am new to the Keycloak community, and I didn't find any threads about my problematic, so sorry if it's a duplicate.
I'm wondering to know how can I perform a "tls_client_auth" client authentication for an external IDP.
Today, the IDP is set to "client secret sent as post" with a ClientId and a ClientSecret. But, for security reinforcment, the provider wants to switch from ClientId/ClientSecret to ClientId/ClientCertificate for mTLS propose following the RFC 8705.
I didn't find the possibility to do that from the admin console in the setting of an external IDP, maybe I am doing something wrong.
The dropdown menu didn't show the possibility to choose the option.
I played with these configurations in keycloak.conf file
Architecture:
What I have:
What I think the provider do:
Links I read:
Thanks for reading and help.
All reactions