TideCloak 0.6.21
This upgrade on top of version 0.6.11, while offering some minor bug fixes and improvements, is mainly introducing a (big) minor release upgrade to Keycloak, from version 26.0.6 to 26.1.0. Coincidently, this release also introduces the small but extremely helpful user-experience improvement of IGA notifications, to let the admin know there are pending changes waiting for action.
Keycloak 26.1.0
Full release notes can be found on Keycloak website. The list below reflects the most relevant changes in the TideCloak context, in descending priority order.
Uniform caching for clustering
Keycloak now moved to jdbc-ping2
transport stack configuration - where unlike previous stacks, this one is supported on all cloud providers. Previous stacks were not supported on Azure and required problematic workarounds.
OpenTelemetry Tracing supported
OpenTelemetry Tracing feature is fully supported and is enabled by default. For more information, see the Enabling Tracing guide.
Dark mode enabled for the welcome theme
Dark mode support for all the Keycloak themes is now enabled. This feature is present in the admin console, account console, login, and on the welcome page. If a user indicates their preference through an operating system setting (e.g. light or dark mode) or a user agent setting, the theme will automatically follow these preferences.
If you are using a custom theme that extends any of the Keycloak themes and are not yet ready to support dark mode, or have styling conflicts that prevent you from implementing dark mode, you can disable support by adding the following property to your theme:
darkMode=false
Sign out all active sessions in admin console now effectively removes all sessions
All sessions, regular and offline, are removed when signing out of all active sessions.
Additional context details for Admin events
Admin events might hold additional details about the context when the event is fired.
Tide's session aligned with Keycloak
Tide's refresh token mechanism is now aligned with Keycloak's one to provide smooth experience. Tide's token also changed to be user-based rather than client-based to allow for a more holistic experience of an SSO where user session can seamlessly transition between different client sessions without the need to reauthenticate.
IGA notifications
A new user interface element was introduced to the Change request
menu and functionality where the Users
, Roles
and Clients
tab heading now have the number of pending change sets appearing to let the user (admin) know.
Stripe library upgrade
Primarily to avoid a critical security vulnerability warning by scanners, the Stripe .net library was upgraded to version 47.3.0. Release notes available in Stripe Github repo.