Skip to content

Releases: cloudtrust/keycloak

18.0.0-CVE-2023-0264-SAML-Back-SLO

17 Apr 09:38

Choose a tag to compare

Keycloak 18.0.0 with backport of:

20.0.5-CVE-2023-0264-SAML-Back-SLO

07 Mar 08:39

Choose a tag to compare

Keycloak 20.0.5 with backport of:

18.0.0-CVE-2023-0264

06 Mar 12:02

Choose a tag to compare

Release 18.0.0 with fix for CVE-2023-0264

8.0.1.artifactbinding-1.2

25 Nov 15:23
a20f3b7

Choose a tag to compare

[CLOUDTRUST-2829] Fix logout issue when token has expired

8.0.1.artifactbinding-1.1

30 Mar 07:11
2710003

Choose a tag to compare

[CLOUDTRUST-2369] Fix Single Log Out

Keycloak 8.0.1 with ArtifactBinding support

23 Jan 13:18

Choose a tag to compare

Update to Keycloak 8.0.1

Eighth release for the Multi-token prototype with Keycloak 7.0.0

07 Nov 14:22

Choose a tag to compare

This release fixes the list of registrators, taking into account the status (enabled or disabled ) of the required actions

Seventh release for the Multi-token prototype with Keycloak 7.0.0

07 Nov 14:20

Choose a tag to compare

This release essentially adds the artifact-binding to the multi-token release

Sixth release for the Multi-token prototype with Keycloak 7.0.0

09 Oct 15:51

Choose a tag to compare

This is not a final prototype for 7.0.0, but a version for initial testing and bug fixing.

This version has the following corrections and features:

  • Improved database credential migration, small change of the credential format as a result
  • Support for legacy json and credential formats
  • Added migration for OPTIONAL flow structures
  • Updates to the GUI for coherence and usability

Fifth release for the Multi-token prototype with Keycloak 7.0.0

30 Sep 13:33

Choose a tag to compare

This is not a final prototype for 7.0.0, but a version for initial testing and bugfixing.

This version has the following corrections and features:

  • Database migration is now correct
  • Credential caching problems should be resolved
  • Only the credential user label is now editable, both through the GUI and through the API
  • Authentication flow exceptions are once again correctly treated and displayed to the user.