Dashboard
Overview of the latest synchronization and application migration.
Latest synchronization
Applications
Configuration
Keycloak and Backupta connections, and synchronization settings. Secrets are never returned to the screen.
Keycloak
Backupta
Email (SMTP)
Used by Keycloak to send the activation emails of the failover (step 1). Saving applies the settings to the Keycloak realm. For a demo without real delivery, run demo-mailbox and point this at localhost:1025.
Synchronization
Okta Backups
The sync uses the active backup: the most recent one at least the safety window old, so a recent Okta incident is not propagated. You can also select one manually.
Users synchronization
Import users, groups and memberships into Keycloak, from the active backup — or from the one you select in the history below. Manual or scheduled.
Actions
History
| Created at | Age | Type | Eligibility | Status | Label |
|---|
Applications migration
Import the applications of the selected CONFIGURATION backup into Keycloak, with their assignments. Catalog apps (OIN, e.g. Google) cannot be migrated here: their SP configuration is not in the backup.
Apps in backup
| Application | Type | Members | Status | Migrated | Priority |
|---|
Failover
Step-by-step cutover from Okta to Keycloak. More steps will be added.
Activate users
Accounts are already active in Keycloak. This sets a random password, forces a change at next login, and emails each user an action link so they set their own password.