Skip to content
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

Provide list of compatible Keycloak releases #5

Open
stianst opened this issue Mar 14, 2024 · 2 comments
Open

Provide list of compatible Keycloak releases #5

stianst opened this issue Mar 14, 2024 · 2 comments

Comments

@stianst
Copy link
Contributor

stianst commented Mar 14, 2024

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:

  • 0.1.0 - Keycloak 22,23,24
  • 0.2.0 - Keycloak 24

Discussion

No response

Motivation

No response

Details

No response

@thomasdarimont
Copy link
Collaborator

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.

@stianst
Copy link
Contributor Author

stianst commented Nov 12, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants