Galaxy migration to support connected experience

If the galaxy security mode is Authentication providers (using Azure AD), the security mode has to be set to “None” (when in non-connected mode), prior to opening the galaxy in connected experience mode. Use the following procedure to migrate an galaxy to use connected experience if:

• You have a galaxy created or modified under System Platform 2023.

• The galaxy is configured with the Authentication providers security mode using Azure AD.

• You want to use Operations Control - connected experience.

This procedure is applicable to both fresh installs of System Platform 2023 R2 and later, and upgrades from System Platform 2023 to later versions of System Platform.

To migrate an existing galaxy that uses Authentication providers security

1. Install or upgrade System Platform, as applicable.

2. Set the License Mode (under Common Platform) to AVEVA Operations Control.

3. Leave the connected experience option disabled.

4. Use the IDE Import function to migrate the existing galaxy to the current version of System Platform. The galaxy Security mode remains set to Authentication providers.

5. Connect to the galaxy.

6. Change the Security mode to None.

7. Open the Configurator and enable connected experience.

8. Connect to the galaxy.

9. Change the Security mode to Authentication providers.

   Note: If you enable connected experience initially (see step 3, above), you will not be able to connect to the galaxy. This is because connected experience uses AVEVA Connect as the federated identity provider, while the galaxy is using Azure AD as the identity provider. In this scenario, when you attempt to connect to the galaxy, you will not be permitted to sign in.