You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could add support some additional metadata in the jar manifest, to allow Keycloak to determine compatibility without having to load the extension form the jar.
Keycloak-Min-Version: 25.0 - min supported Keycloak Version
Keycloak-Max-Version: 26.0 - max supported Keycloak Version,
Keycloak-Features-Required: oid4vci
Instead of using a jar Manifest, we could also let an extension provide some Java class that provides that metadata, either via a simple API or via Annotations.
We could add support some additional metadata in the jar manifest, to allow Keycloak to determine compatibility without having to load the extension form the jar.
Keycloak-Min-Version: 25.0 - min supported Keycloak Version Keycloak-Max-Version: 26.0 - max supported Keycloak Version, Keycloak-Features-Required: oid4vci
Instead of using a jar Manifest, we could also let an extension provide some Java class that provides that metadata, either via a simple API or via Annotations.
Min-version could be for sure, but don't think max-version should be.
For supported versions of Keycloak we could instead just rely on testing. If a provider has sufficient tests, and we have some GitHub Actions magic to test the current release with a KC version, then we can "certify" a provider with a new release, without having to always release all providers to support a new KC version.
Description
Automatically provide lists of what versions of Keycloak a given release of the extension is compatible with.
An extension may have multiple releases, and each release may have different versions of Keycloak it is compatible with.
For example:
Discussion
No response
Motivation
No response
Details
No response
The text was updated successfully, but these errors were encountered: