Skip to main content

Digitanium to Shift Migration Flow & BDDK Example Flow

Digitanium to Shift Migration Flow​

The migration flow allows existing Digitanium (SSMS) users to transition to a Shift (Maverick) backend. This is a multi-step process starting with a valid SSMS activation and login, obtaining a Shift activation code, switching environments, completing activation in Shift, and optionally obtaining authorization tokens for backend services.

High-Level Flow Overview​

Step 1: SSMS Login​

  • StartLoginEvent → LoginResultEvent

Step 2: Get Shift Activation Code​

  • Use SSMS login to obtain activation code for Shift

Step 3: Switch to Shift Environment​

  • Switch to Shift server assets, perform RestartEvent

Step 4: Shift Activation​

  • KSSIDP.activate(...) or SetAuthorisationCodeEvent → SetAuthorisationCodeResultEvent

Step 5: Exchange IAM Token (Optional)​

  • ExchangeIamTokenEvent → ExchangeIamTokenResultEvent (retrieve token for authorizing special requests to backend services)

Step 5b: Get IAM Token Claims (Optional)​

  • GetIamAccessTokenClaimsEvent → GetIamAccessTokenClaimsResultEvent (check claims and permissions of the IAM token)

Step 6: Delete SSMS User & Complete Migration​

  • Delete legacy SSMS user from system → Migration Complete

Example Flow Migration Existing Users​

An existing user can be migrated like follows:

Example Login Flow With Transaction​