Repository navigation
Replies: 3 comments 3 replies
|
+1 for adding this in the server to support non-operator deployments. I think any implementation needs to take into account Similarly, I would like an SPI option or CLI option to enable/disable importing (maybe default to enabled, as we check the file exists), rather than just the |
|
I'm not 100% if this should be a priority, as it would behave identical to the already existing So is this "just" a convenience option? I acknowledge that we want to make things simple. Wouldn't it confuse people where there are different options to achieve the same thing? I'm +100 to have an option to disable the automated import. Some security nerds might be very annoyed that we're putting all certificates in a single trust store when they would like to have distinct trusted certificates for specific use cases. |
|
Created a ticket for the implementation: #42900 |
Uh oh!
There was an error while loading. Please reload this page.
Hey @ryanemerson @ahus1 @shawkins 👋🏻
Following up on the discussion in the Signed JWT Thread (here and here), I'd like to establish the path forward for Kubernetes CA initialization.
At the moment, the Kubernetes CA is added by the Operator to the array of Trusted CAs:
keycloak/operator/src/main/java/org/keycloak/operator/controllers/KeycloakDeploymentDependentResource.java
Lines 468 to 476 in 6e7a836
This approach works great but is limiting to the environments that don't use the Operator - such as the UDS Platform. Therefore, I suggest to move this logic directly to Keycloak - similarly to what I did in my previous Kubernetes Signed JWT Pull Request here:
The above proposal makes the setup much easier for the non-operator users.
All reactions