Repository navigation
Keycloak 21| My project overriding this version | Not able to configure new application with three certificates in metadata #50620
Unanswered
RuchiSingh18
asked this question in
Q&A
Replies: 0 comments
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.
Uh oh!
There was an error while loading. Please reload this page.
We are facing an issue with the RSA signing keys configuration.
Currently, there are three RSA keys:
Two fallback keys
One primary key
Questions/Concerns
We are unsure which signing certificate is currently being used by the customer across their 200+ applications. The existing key configuration does not appear to be correct, yet the customer has been using these applications successfully since they were configured in 2021.
The customer is now trying to configure a new application. However, the IdP metadata contains all three certificates, and the service provider is not allowing the configuration because of the multiple signing certificates.
Is there a way to identify which applications are using which signing certificate? We believe that removing the fallback certificates may be required to configure the new application, but before making any changes, we need to understand whether any existing applications still rely on those certificates.
Could you please advise if there is a way to determine which applications are associated with each signing certificate, or recommend the best approach for safely removing the fallback certificates?
For ref:
fallback certificate :
Normal certificate:
All reactions