Skip to content

KEYCLOAK-19747 - Support for different key uses by authentication protocol#8684

Closed
laskasn wants to merge 2 commits intokeycloak:mainfrom
eosc-kc:110-keyuses-2ndPR
Closed

KEYCLOAK-19747 - Support for different key uses by authentication protocol#8684
laskasn wants to merge 2 commits intokeycloak:mainfrom
eosc-kc:110-keyuses-2ndPR

Conversation

@laskasn
Copy link
Copy Markdown
Contributor

@laskasn laskasn commented Nov 2, 2021

A description of this pull request is available here.
The relevant ticket is this one

@mposolda
Copy link
Copy Markdown
Contributor

mposolda commented Aug 7, 2023

@laskasn CC @cgeorgilakis There are some changes in latest Keycloak related to keys and key use etc. Just to confirm, could you please doublecheck if latest Keycloak 22.0.1 doesn't already address your use-case?

@cgeorgilakis
Copy link
Copy Markdown
Contributor

@laskasn CC @cgeorgilakis There are some changes in latest Keycloak related to keys and key use etc. Just to confirm, could you please doublecheck if latest Keycloak 22.0.1 doesn't already address your use-case?

@mposolda what we want is not supported yet in Keycloak.
We want to support different keys per protocol (OIDC, SAML). SAML and OIDC certificates typically have different rotation requirements, i.e. in SAML every 10 years while in OIDC every 6 six months. For details see related jira ticket and related github discussion.

If you want to proceed with this PR, we need to rebase it and move ui changes from old admin console to new admin console.

@stianst
Copy link
Copy Markdown
Contributor

stianst commented Mar 15, 2024

With the complexity/size of this PR and fairly low priority this is not going to get reviewed/merged, so I'm going to close this at least for now.

I don't think it is needed to be able to use the same keys for enc and sig, and also don't think it really is needed to be able to support different keys per protocol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants