Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To upgrade the version of WSO2 Identity Server, the user store database should be upgraded. Note that there are no registry schema changes between versions. This topic provides instructions on how you can upgrade (the data and configurations) from WSO2 Identity Server 4.1.0 to WSO2 Identity Server 4.6.0. 

Table of Contents

...

  • Before you upgrade to the latest version of WSO2 Identity Server, you create a staging database, which is essentially an empty database. Note that you should NOT connect a new version of WSO2 IS to an older database that has not been migrated.
  • Make backups of the database and the WSO2 product prior to upgrading the database. The backup can be taken by copying the home folder of the product.
  • Stop all the WSO2 products that are connected to the database.
  • If any files/folders are changing in the product pack to which you are upgrading, you need to make a backup of the relevant files/folders prior to changes.

...

  1. Log in to the new Identity Server and go to the entitlement management console. Note that the XACML policies are not visible in this screen.

  2. To perform the migration of XACML policies, download this migration tool.
  3. In the migration tool you downloaded, set up the configuration parameters using the config.properties file which can be found in the <ROOT>/resources directory.

  4. Execute the following command to start the migration.

    On Windows

    Code Block
    migratePolicies.bat


    On Linux

    Code Block
    ./migratePolicies.sh
    Note

    OAuth applications, which were created in the tenants are also created inside the super admin space. This is because, IS 4.1.0 did not support tenant partitioning for OAuth applications. If there are OAuth apps available in the tenant space, you have to manually include them inside the tenant space once the migration process is done.

Recommended checkpoints

The databases should contain the newly added tables, which are namely as follows:

  • UM_DOMAINACCOUNT_MAPPING 

  • UM_DOMAIN 

  • UM_MODULE 

  • UM_MODULE_ACTIONS 

  • UM_SYSTEMSHARED_USER_ROLE 

  • UM_SYSTEM_ROLEROLE 

  • UM_SYSTEM_USER_ROLEIDP_BASE_TABLEUSER 

  • UM_SYSTEM_USER_ROLE 

  • UM_TENANT_IDPIDP 

  • UM_TENANT_IDP_ROLESROLES 

  • UM_TENANT_IDP_ROLE_MAPPINGSMAPPINGS 

  • IDP_BASE_TABLE 

  • IDN_IDENTITY_THRIFTMETA_SESSIONDATA 

  • IDN_IDENTITY_USER_DATADATA 

  • IDN_IDENTITYTHRIFT_META_DATASESSION

Going into production

The following are recommended tests to run on the staging system. 

...