Tutorial: Configure Adobe Identity Management (OIDC) for automatic user provisioning with Azure Active Directory – Microsoft Entra

Table of Contents0.1 In this article1 Capabilities supported2 Prerequisites3 Step 1. Plan your provisioning deployment4 Step 2. Configure Adobe Identity Management (OIDC) to support provisioning with Azure AD5 Step 3. Add Adobe Identity Management (OIDC) from the Azure AD application gallery6 Step 4. Define who will be in scope for […]

This tutorial describes the steps you need to perform in both Adobe Identity Management (OIDC) and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to Adobe Identity Management (OIDC) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory.

Capabilities supported

  • Create users in Adobe Identity Management (OIDC)
  • Disable users in Adobe Identity Management (OIDC) when they do not require access anymore
  • Keep user attributes synchronized between Azure AD and Adobe Identity Management (OIDC)
  • Provision groups and group memberships in Adobe Identity Management (OIDC)
  • Single sign-on to Adobe Identity Management (OIDC) (recommended)

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following prerequisites:

  • An Azure AD tenant.
  • A user account in Azure AD with permission to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
  • A federated directory in the Adobe Admin Console with verified domains.
  • Review the adobe documentation on user provisioning

Note

If your organization uses the User Sync Tool or a UMAPI integration, you must first pause the integration. Then, add Azure AD automatic provisioning to automate user management from the Azure Portal. Once Azure AD automatic provisioning is configured and running, you can completely remove the User Sync Tool or UMAPI integration.

Step 1. Plan your provisioning deployment

  1. Learn about how the provisioning service works.
  2. Determine who will be in scope for provisioning.
  3. Determine what data to map between Azure AD and Adobe Identity Management (OIDC).

Step 2. Configure Adobe Identity Management (OIDC) to support provisioning with Azure AD

  1. Login to Adobe Admin Console. Navigate to Settings > Directory Details > Sync.

  2. Click Add Sync.

    Add

  3. Select Sync users from Microsoft Azure and click Next.

    Screenshot that shows 'Sync users from Microsoft Azure Active Directory' selected.

  4. Copy and save the Tenant URL and the Secret token. These values will be entered in the Tenant URL and Secret Token fields in the Provisioning tab of your Adobe Identity Management (OIDC) application in the Azure portal.

    Sync

Add Adobe Identity Management (OIDC) from the Azure AD application gallery to start managing provisioning to Adobe Identity Management (OIDC). If you have previously setup Adobe Identity Management (OIDC) for SSO, you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4. Define who will be in scope for provisioning

The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described here.

Step 5. Configure automatic user provisioning to Adobe Identity Management (OIDC)

This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.

To configure automatic user provisioning for Adobe Identity Management (OIDC) in Azure AD:

  1. Sign in to the Azure portal. Select Enterprise Applications, then select All applications.

    Enterprise applications blade

  2. In the applications list, select Adobe Identity Management (OIDC).

    The Adobe Identity Management (OIDC) link in the Applications list

  3. Select the Provisioning tab.

    Provisioning tab

  4. Set the Provisioning Mode to Automatic.

    Provisioning tab automatic

  5. Under the Admin Credentials section, input your Adobe Identity Management (OIDC) Tenant URL and Secret Token retrieved earlier from Step 2. Click Test Connection to ensure Azure AD can connect to Adobe Identity Management (OIDC). If the connection fails, ensure your Adobe Identity Management (OIDC) account has Admin permissions and try again.

    Token

  6. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.

    Notification Email

  7. Select Save.

  8. Under the Mappings section, select Synchronize Azure Active Directory Users to Adobe Identity Management (OIDC).

  9. Review the user attributes that are synchronized from Azure AD to Adobe Identity Management (OIDC) in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Adobe Identity Management (OIDC) for update operations. If you choose to change the matching target attribute, you will need to ensure that the Adobe Identity Management (OIDC) API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Adobe Identity Management (OIDC)
    userName String
    active Boolean
    emails[type eq “work”].value String
    addresses[type eq “work”].country String
    name.givenName String
    name.familyName String
    urn:ietf:params:scim:schemas:extension:Adobe:2.0:User:emailAliases String
  10. Under the Mappings section, select Synchronize Azure Active Directory Groups to Adobe Identity Management (OIDC).

  11. Review the group attributes that are synchronized from Azure AD to Adobe Identity Management (OIDC) in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the groups in Adobe Identity Management (OIDC) for update operations. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Adobe Identity Management (OIDC)
    displayName String
    members Reference
  12. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  13. To enable the Azure AD provisioning service for Adobe Identity Management (OIDC), change the Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

  14. Define the users and/or groups that you would like to provision to Adobe Identity Management (OIDC) by choosing the desired values in Scope in the Settings section.

    Provisioning Scope

  15. When you are ready to provision, click Save.

    Saving Provisioning Configuration

This operation starts the initial synchronization cycle of all users and groups defined in Scope in the Settings section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.

Step 6. Monitor your deployment

Once you’ve configured provisioning, use the following resources to monitor your deployment:

  • Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
  • Check the progress bar to see the status of the provisioning cycle and how close it is to completion
  • If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

More resources

Next steps

Source Article

Next Post

Data lifecycle management - Cloud Adoption Framework

Thu Jun 23 , 2022
Table of Contents0.1 In this article1 Lifecycle of data2 Managing data lifecycles3 Next steps Article 04/19/2022 2 minutes to read 2 contributors In this article Data lifecycle management is the practice of using certain policies to effectively manage […]