Azure Active Directory Settings

Azure Active Directory can be used as a user provider for creating a repository in AVEVA Work Tasks and can also be used to access AVEVA Work Tasks Pro app through Azure Active Directory.

Before configuring the Azure Active Directory settings in AVEVA Work Tasks, register the app in Microsoft Azure directory.

App Registration

You need to register the app in Microsoft Azure to generate the Client Id, Tenant Id, and Object Id.

To register the App:

1. Access the Microsoft Azure portal.

2. Click View under Manage Azure Active Directory on the Microsoft Azure Home page.

3. Click App registrations in the left navigation pane.

4. Click New registration tab.

   1. In the Name box, enter the display name for this application.

   2. For Supported account types, select Accounts in this organizational directory only (AVEVA Solutions Limited only - single tenant).

   3. For Redirect URI (optional), specify the URI to get the authentication response.

5. Click Register.

   The app is registered in the Azure Directory.

Azure Active Directory Settings

In AVEVA Work Tasks, you can configure Azure Active Directory using the Farm Configuration Wizard. With this setting, the user is authenticated against Azure Active Directory provider and can access the AVEVA Work Tasks features.

To Configure Azure Active Directory Settings

6. On the Windows Start menu, point to Programs, point to AVEVA, point to Work Tasks, and then click Farm Configuration Wizard.

   The AVEVA Work Tasks Farm Configuration Wizard appears.

7. Click Next.

   The Edit AVEVA Work Tasks Farm Settings window appears.

8. Select Service settings.

   The Enterprise Server settings can be selected if the Farm Server Installation is using Enterprise Server Installation.

9. Click Next.

   The Services/Global Settings window appears.

10. Click against Global Settings.

11. In the Global Settings window, select OpenID Settings tab.

12. In the Authentication Provider drop-down list, select Azure Active Directory.

13. In the Tenant ID box, enter the tenant ID of the Azure Active Directory instance.

14. In the Client ID box, enter the client ID of the Azure Active Directory instance.

15. In the Client Secret box, enter the client secret key of the Azure Active Directory instance.

16. Click Save and then click OK.

Note:
- If you log out from the Central Configuration (CC) site, you are also logged out from the Enterprise Console (EC) site. To access the EC site again, you need to access the EC URL, provide the access credentials, and then continue to use the EC site.

- The Azure Active Directory provider is listed in the Resource Provider drop-down list. But if you create the repository with this Azure Active Directory provider, it will work only when you configure Azure Active Directory through the Farm Configuration Wizard.

- Once you configure Azure Active Directory from Farm Configuration Wizard,
-- the Application Pool of Central Configuration changes to AVEVA Work Tasks Integrated Mode.
-- while accessing the Enterprise Console and Central Configuration, you are redirected to the Microsoft Online Page for authentication.

- When the environment is configured to Azure Active Directory, the following are not supported:
-- Synchronize Users
-- Electronic Signature
-- Disable Users from Azure Active Directory
-- Security Workflow
-- Wizard for Human Activities (In Assign Actors property of Human Activities while building the filter condition, the ‘IN’ and ‘Not In’ operators are not supported.)
-- Role Condition Set through Filter Condition of To Property in the Human Activity
-- The user’s display name with characters like # and ^
-- System Platform IDE

- The user or role search uses the starting character that you enter and does not have any search.

- You cannot have both the AVEVA Identity Manager (AIM) and Azure Active Directory user providers together.

- Scheduler Event Association installed through package does not work in Azure Active Directory when logged-in user's display name has special characters.

- It is recommended to use https sites for Azure Active Directory repository.