TideCloak 0.5.8
Keycloak version 26.0.6
Lots and lots of updates. Detailed release notes here.
Migration mode
The enviroment variable IS_MIGRATION
now places TideCloak in a database migration mode to allow all TideCloak's specific extensions to complete upgrading the database from previous versions. Upgrading / Migrating now between versions requires the following steps:
- Shut down all TideCloak instances
- Set the variable
IS_MIGRATION
totrue
- Start one instance of TideCloak with the new version
- Observe and review console log entries to verify successful data migration
- Once done and server is ready, shut down the server
- Set the variable to
false
or remove it altogether. - Start all instances of TideCloak as usual.
Continious rebase with Keycloak's admin-UI
New mechanism implemented to allow for on-going, continious integration between TideCloak custom admin-UI to Keycloak's admin-UI.
Backend licensing sync
Updated Midgard backend service to manage all licensing communications with Stripe to allow M2M auto-provisioning and non-interactive updates. All Admin console licensing management now handled through Midgard backend processes.
ORK authenticity proof
New Midgard tool now signs the ORK's public URL with Tide's Cybersecurity Fabric private key to guarantee no rogue ORK can inject itself into the network without authorisation. All ORKs are now required to present new authenticity proof when registering to the network (for the network to divert traffic).