Which UI do you use?

Custom UI

Pre built UI

Upgrading user's core version

• Tables to update:
  • apps (update core_version, plugin_interface_versio and plugin_version)
  • aws_containers (update image_version)
• System Manager:
  • Find instance id
  • Find StartUpdateSuperTokens command for relevant app
  • Copy to new
  • Change imageVersion parameter
  • Make sure the Document version is relevant to the new core version
  • Run command and check the container is updated and running

Core DB Migration

3.3 to 3.4

• No change

3.4 to 3.5

• Change user_id in emailverification_verified_emails to VARCHAR(128)
• Change user_id in emailverification_tokens to VARCHAR(128)
• Add new table (use the db_user associated with user's core or remember to change the owner of the new tables to db_user):

  CREATE TABLE IF NOT EXISTS all_auth_recipe_users(
     user_id CHAR(36) NOT NULL,
     recipe_id VARCHAR(128) NOT NULL,
     time_joined BIGINT NOT NULL,
     PRIMARY KEY (user_id)
  );
  CREATE INDEX all_auth_recipe_users_pagination_index ON all_auth_recipe_users (time_joined DESC, user_id DESC);

  This means that the content from other emailpassword_users and from thirdparty_users need to be copied into this table
• Deleted index emailpassword_user_pagination_index and thirdparty_users_pagination_index

3.5 to 3.6

• No manual change required

3.6 to 3.7

• No manual change required

3.7 to 3.8

• No manual change required
• Adds new tables for passwordless (is added automatically):
  • passwordless_users that stores the users of the passwordless recipe
  • passwordless_devices that stores devices/information about passwordless login attempts
  • passwordless_codes that stores the codes each device can consume to finish the login process

3.8 to 3.9

• No manual change required

3.9 to 3.10

• No manual change required

3.10 to 3.11

• No manual change required

3.11 to 3.12

• No manual change required

3.12 to 3.13

• No manual change required

3.13 to 3.14

• No manual change required

3.14 to 3.15

• No manual change required

3.15 to 3.16

• No manual change required

3.16 to 4.0

• Run: ALTER TABLE thirdparty_users ALTER COLUMN third_party_user_id TYPE VARCHAR(256); ALTER TABLE emailpassword_users ALTER COLUMN password_hash TYPE VARCHAR(256);

4.0 to 4.1

• No manual change required

4.1 to 4.2

• No manual change required

4.2 to 4.3

• No manual change required

4.3 to 4.4

• No manual change required

4.4 to 4.5

• No manual change required

4.5 to 4.6

• No manual change required

4.6 to 5.0

• Renamed access_token_signing_key_update_interval to access_token_dynamic_signing_key_update_interval in config
• If access_token_signing_key_dynamic is currently set to false then run:

  ALTER TABLE session_info ADD COLUMN use_static_key BOOLEAN NOT NULL DEFAULT(true);
  INSERT INTO jwt_signing_keys(key_id, key_string, algorithm, created_at)
     select CONCAT('s-', created_at_time) as key_id, value as key_string, 'RS256' as algorithm, created_at_time as created_at
     from session_access_token_signing_keys;

• If access_token_signing_key_dynamic is currently set to true, or it not set at all:

  ALTER TABLE session_info ADD COLUMN use_static_key BOOLEAN NOT NULL DEFAULT(false);