-
Notifications
You must be signed in to change notification settings - Fork 7.9k
fix: making cert lookup spi public #45010
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
There appears to be an unrelated CRDTest expectation change - which doesn't seem to occur for me locally. If needed that can be separated to a different pr. EDIT: moved the other commit to its own pr. |
closes: keycloak#33818 Signed-off-by: Steve Hawkins <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.passwordless.PasskeysKcOidcFirstBrokerLoginTest#testLinkAccountByReauthenticationWithDiscoverablePasskey |
vmuzikar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would probably need some docs to officially consider it supported.
That seemed optional as there appear to be quite a few non-internal spis not covered by https://www.keycloak.org/docs/latest/server_development/index.html Or is there another place where this should be documented? |
AFAIU, those not mentioned in the docs are not officially supported.
No, this would be it. I think we have some grey area though. We have public SPIs, yet we don't document them, and hence don't support them. I do not know then why we even mark SPIs as public. Adding a new supported SPI is a bigger step and would require broader team involvement, IMHO. We could potentially just mark the cert lookup SPI as public and not mention it in the release notes not to give any implication it's supported. Not sure if that makes much difference though from a private SPI. CC @stianst |
Rationale for this change:
On timing, this is optional for 26.5.
closes: #33818