Connect to a galaxy
- Last UpdatedSep 10, 2024
- 1 minute read
Once you have started the IDE, you can connect to a galaxy. The process for connecting to a galaxy in connected experience mode is similar to the process for connecting to a galaxy where connected experience is not enabled. See Connect to a Galaxy for more information.
Galaxy migration to support connected experience
When you open an existing galaxy that was configured with the security mode set to Authentication providers (using Azure AD), you must set the security mode to “None” (when in non-connected mode), prior to opening the galaxy in connected experience mode. Connected experience mode is enabled and disabled under License Mode, in the System Platform Configurator. See License mode for details.
Failure to connect to the galaxy
However, the internal system checks are different when connected experience is enabled. You will not be able to connect to the galaxy if:
-
Operations Control mode is not enabled on the GR node.
-
The galaxy has a security mode that is not compatible with Operations Control connected experience mode. The only compatible security modes are None and Authentication Provider.
-
The credentials you used to log into the IDE do not give you authorization to open the galaxy. In this case, you must restart the IDE and enter the correct credentials.
Successfully connect to the galaxy
The galaxy will open if the above system checks allow you to connect to an existing galaxy or create a new galaxy.
-
Your user information will be shown in the IDE.
-
AVEVA Connect records that you are using the IDE.
For details about creating a galaxy, see Create a Galaxy.