Known issues - AVEVA OMI 2023 R2 SP1

Issue Number

Description

Security mismatch

Some connected experience configuration scenarios can result in unexpected behavior.

Scenario 1: Ability to access security tabs when an unsupported authentication mode has been configured.

If a galaxy using Galaxy security has been created without connected experience, and then connected experience is configured, if you:

1. Connect to the galaxy and change the authentication mode to Authentication Providers.

2. Add a new group and cancel the changes.

   You will be able to access the security tabs in an unsupported authentication mode.

Scenario 2: Cancelling read-only message box in the security editor closes the IDE.

If a galaxy using Galaxy security has been created without connected experience, then the IDE is closed, and then you configure connected experience and login to the IDE with an AVEVA Connect user, when you:

3. Connect to the galaxy and click Yes when the dialog appears.

4. Launch a second instance of the IDE and connect to the same galaxy.

5. Navigate to the security page in the second IDE. A dialog opens and asks if you want to open in read-only mode.

6. Click No.

   The IDE closes (the IDE should not close in this scenario).

Scenario 3: The Authentication Providers security mode can be enabled without configuring any roles.

If you connect to a galaxy and select Authentication Provider security, and then navigate to the Roles tab, but:

7. You do not add any roles.

8. Click Save.

   The IDE will shut down. Note that changes should not be allowed in this scenario since no role is configured and there is no Administrator login support under Operations Control mode.

IMS 2897808

The SignedAlarmAck feature is not currently supported for Application Server and AVEVA OMI when AVEVA Operations Control connected experience is configured. Attempting to sign an alarm acknowledgement fails, and an error message is generated that warns of incorrect user credentials.

IMS 1869732

If the domain controller goes down and at the same time, an IDE user attempts to perform a change user operation, there is a slight possibility that Windows will display a crash dialog for the IDE. Note: This is a very rare scenario.

Workaround: Restart the IDE to proceed.

IMS 1861501

Endpoints on remote nodes, including redundant SSO nodes, are not discovered when the Global Discovery Server is not available. As a result, logging in to a Galaxy using Azure AD credentials when the security mode is Authentication Provider is not successful.

Workaround: For discovery of any endpoints that are not on the local node, then a GDS (global discovery) server MUST be available for discovery. You can configure a secondary GDS to avoid non-discovery, which can occur when the redundant SSO is on a different node. You can configure secondary discovery servers in the System Platform IDE. See the Application Server help for instructions on configuring multi-galaxy communication. You can also configure a secondary discovery server through the PCS Configuration utility.

9. Open the PCS Services Configuration utility
   C:\Program Files (x86)\Common Files\ArchestrA\Services\aaServiceConfiguration.exe

10. Open the Configure link (near the top of the utility window), the select Discovery Service from the menu.

11. Enter a secondary node name for both the Local and Cross solution.

    "Local solution" is equivalent to Local Galaxy server in the System Platform IDE, and "Cross solution" is equivalent to Multi-Galaxy server.

IMS 1846869

When System Platform is configured with a standalone System Management Server (SMS) and Authentication Provider, other nodes pointing to the SMS node may not be able to reach the Authentication Provider on the SMS node for user authentication.

Workaround: Use one of the recommended SMS system configurations described in the System Platform Installation Guide.

IMS 1842703

If, after configuring a node to connect to an existing System Management Server, you choose to make the node a redundant SSO server, the Configurator does not indicate that the Authentication Provider configuration parameters must be configured (green checkmark is still shown and the Configure button is grayed out).

Workaround: Select the Authentication Provider configuration option and configure the parameters as described in the System Platform Installation Guide.

CR L00138837

AppEngine can crash due to calls made to API dlls even when using try/catch. This issue is specific to Nullable data types. The recommendation is to use wrapped API DLLs in Application Server scripting.

TFS 1404918

If a network failure occurs on the active engine node and Warm Redundancy is enabled, the last value is shown as NULL for slow-changing Tags.

Workaround: Perform a SQL Insert or CSV Insert for the tag in question on the Historian side. This will restore the value in the Historian trend.