Switch users in AIM

The objective is to improve product functionality by enabling operators to switch users seamlessly when using AVEVA Identity Manager (AIM). When an operator attempts to switch to a new user and the sign in fails, the current user remains signed in. Switching users in AIM ensures uninterrupted access to the product and prevents unintended logouts during user-switching attempts.

Products that use AIM currently switch users by first signing out the active user and then signing in the new user. If this process fails, the application continues to use cached authentication information.

Note: If a user-switch attempt fails, the previous user remains signed in and can continue using the application. However, Single Sign-On (SSO) with other AVEVA applications on the same system is unavailable until a user successfully signs in.

The following list describes different user scenarios and outcomes that can occur when a user switches accounts:

1. Scenario 1: Successful user switch

   • Description

     • The user initiates a user switch.

     • The new user logs in successfully. 

   • Outcome

     • The new user becomes the active user for the application and Single Sign-On (SSO).

     • The original user is logged out. 

2. Scenario 2: Unsuccessful switch (New user sign in fails)

   • Description

     • The user initiates a user switch.

     • The new user sign in attempt fails. 

   • Outcome

     • If the existing authentication token is valid, the original user remains logged in.

     • No active SSO session is available.

3. Scenario 3: New user lacks permissions

   • Description

     • The user successfully logs in to CONNECT.

     • The user does not have the required permissions for the application. 

   • Outcome

     • The sign in is treated as successful.

     • The new user credentials are added to the SSO session.

4. Scenario 4: Switch cancelled

   • Description

     • The user initiates a user switch.

     • The user cancels the operation before completion. 

   • Outcome

     • The original user remains logged in using cached authentication tokens.

     • An active SSO session might not be available if the logout process was already completed. 

Switch to another user in WindowViewer

5. In WindowViewer, go to Special , select Security, and then select Log On. The system prompts you to authenticate with AVEVA Identity Manager.

6. Enter the second user name and select Next.

7. In the Password field, enter the password, and then select Sign in.

   The access level and the operator ID are updated.

Note: If authentication for the second user fails, the original user remains signed in.