Add https-client-auth configuration to Keycloak deployments#62
Add https-client-auth configuration to Keycloak deployments#62akostadinov wants to merge 1 commit into3scale-qe:mainfrom
Conversation
Configure all Keycloak deployments (RHBK, RHSSO, and keycloak-deployment) to request client certificates for HTTPS connections by adding the https-client-auth=request option. This enables mutual TLS authentication when clients provide certificates. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
Cant this be set up per realm? This will break existing tests |
|
This is a setting on the TLS level to request a client certificate optionally. At the moment of TLS connection, there is no way to know what realm the client would be accessing. Presently ssl-rhbk has the setting and it doesn't appear to break any functionality, only now MTLS is possible to configure. |
|
Ok, just tested |
|
I think it is alright to keep the option in case it gets deployed with a TLS endpoint at some point. But let me know if you want this removed. |
|
Also if you have the tools running somewhere, pls let me know so I see that the changes are in fact properly in effect. |
Configure all Keycloak deployments (RHBK, RHSSO, and keycloak-deployment) to request client certificates for HTTPS connections by adding the https-client-auth=request option. This enables mutual TLS authentication when clients provide certificates.
🤖 Generated with Claude Code
Needs to be tested first!