Repository navigation
Replies: 1 comment
|
You mean your external partners use self-signed certificates that are not known beforehand? I don't think this will work. But with certificates signed by trusted CAs, all the CA certificates should already be be available. |
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.
Hi ,
We are looking for adding certficaes to the keycloack truststore to secure outgoing connection dynamically . the supported method for configuring a truststore for external TLS as provided here is as follows:
bin/kc.[sh|bat] start --spi-truststore-file-file=myTrustStore.jks --spi-truststore-file-password=password --spi-truststore-file-hostname-verification-policy=ANY
I am working on a use case where all the external certs are not known beforehand. An example could be adding a new IDP provider on a running keycloack instance.
Is there a a runtime configuration possible of such external certificates ?
All reactions