Log in to Management Center

You can log in to Management Center in one of the following authentication modes: Enterprise, Local, or Hybrid mode. In Local mode, you can provide the user credentials to log in to Management Center. In Enterprise mode, users can provide user credentials and the users will be added to Management Center via auto-registration. However, you must ensure that the group to which the user belongs must already be there in Management Center. In Hybrid mode, you can provide the user credentials or use the Active Directory credentials to log in to Management Center. For more information on auto-registration, see the topic Auto registration of Enterprise users.

Log in to Management Center

1. Launch the application.

   The AVEVA Identity Manager page appears on the browser.

   

2. Enter the credentials to log in and select Sign In.

3. If you are an Azure Active Directory user, then you will be redirected to the Azure portal. Enter your Azure credentials and select Sign-in.

4. Optional: If you are an Active Directory user, you can use the Windows integrated login button to log in to Management Center.

   Note: You may be prompted to enter the Windows credentials to log in.

5. Select the required Plant from the drop-down list.

   You must be able to access the application after selecting the Plant.

   Note:
   - When you close the Management Center, you must log out of the AVEVA Identity Manager or close all the browsers. If you do not log out or close the browsers, relaunching the Management Center application will log you in automatically.
   - An Active Directory user will not be allowed to log in to Management Center with a local password. The Active Directory user can, however, use the Windows Integrated Login check box to login to Management Center.
   - In Azure Active Directory configuration, if an existing Active Directory user is mapped to a group (on-premises Active Directory or Local group), that user can access the features to which the group has permissions. If you want to restrict the user from accessing those features, you can do the following via Permission Manager after upgrading to AVEVA Mobile Operator 2020 R2 or later:
   - If the Active Directory user is associated with Active Directory group, then delete the Active Directory group.
   - If the Active Directory user is associated with a Local group, then either disassociate the link between the Active Directory user and the Local group or delete the Local group