Identity Provider

Note:
- For enterprise authentication mode, it is recommended to remove Identity Provider if it is already installed. For more information about configuration, see Federated Identity Provider.
- If you upgrade from AVEVA Mobile Operator 2020 R1 or AVEVA Mobile Operator 2020 R2, you must reconfigure the Identity Provider.

Steps:

1. From the Configurator window, select Identity Provider.

2. From the Identity Provider drop-down list, select the required option.

   1. Select None to remove Mobile Operator Local / Active Directory configuration.

   2. Select Local \ Active Directory to support local users or Active Directory users with local password.

      Server Name: Enter the database instance name.

      Database Name: Enter the database name.

      Authentication: Select the required authentication, 'Windows Authentication' or 'SQL Server Authentication'.

      • User Name: The username to access the database.

        Note: It is recommended to use the UserName mapped to MORServerRole.

      • Password: The password to access the database.

        Encrypt Database Connection: If required, select the Encrypt Database Connection checkbox.

        Note: If you wish to encrypt your database connection, you must also select Yes for Force encryption and select the desired certificate in the SQL Server Configuration Manager. For more information, see the Microsoft documentation.

3. Press the Configure button.

   The configuration process continues and you can see the status of the configuration in the Configuration Messages box. If any error or warning messages appears in the Configuration Message box, then you must resolve the issues.

Following are few points that you must keep in mind for Identity Provider:

• After upgrading to AVEVA Mobile Operator 2020 R1 and later releases, you may have to reconfigure the Identity Provider.

• If you switch the authentication modes in the AVEVA Mobile Operator web application, then you must reconfigure the Identity Provider in the configurator. Specifically:

  • If the authentication mode is Local or Hybrid, then Identity Provider must be configured as 'Local\Active Directory'.

  • If the authentication mode is Enterprise, then Identity Provider must be configured as Azure Active Directory or CONNECT or None.

• When you upgrade a database to AVEVA Mobile Operator 2020 R2 and later versions, and select the Enterprise mode with Identity Provider configured as Azure Active Directory, then 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 after the upgrade:

  • If the Active Directory user is associated with Active Directory group, then delete the Active Directory group from the database.

  • 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.