Configuring Azure Active Directory as a SAML Identity Provider

Note: Pivotal Platform is now part of VMware Tanzu. In v1.12 and later, Pivotal Single Sign‑On is named Single Sign‑On for VMware Tanzu.

This topic describes how to set up Azure Active Directory (AD) as your identity provider by configuring SAML integration in both Single Sign‑On for VMware Tanzu and Azure AD.

Step 1: Set up SAML in Single Sign‑On

  1. Log in to the SSO Operator Dashboard at https://p-identity.SYSTEM-DOMAIN as a Plan Administrator.

  2. Select your plan and click Manage Identity Providers on the drop-down menu.

    Azure manage id providers

  3. Click Configure SAML Service Provider.

    Azure config saml service provider

  4. (Optional) Select Perform signed authentication requests to enforce SSO private key signature and identity provider validation.

    Saml auth checkbox

  5. (Optional) Select Require signed assertions to validate the origin of signed responses.

  6. Click Download Metadata to download the service provider metadata.

  7. Click Save.

Step 2: Set up SAML in Azure AD

  1. Log in to Azure AD as a Global Administrator at https://portal.azure.com/.

  2. Navigate to Azure Active Directory tab > Enterprise application.

    The information depicted in this screenshot is described in the step above.

  3. Select Non-gallery application. Provide a name and click Add.

    The information depicted in this screenshot is described in the step above.

  4. Navigate to Azure Active Directory > Enterprise applications.

    The information depicted in this screenshot is described in the step above.

  5. Click your app and then click the Single sign-on tab.

  6. Select SAML-based Sign-on from the dropdown and then click Upload metadata file to upload the metadata file you downloaded from step 6 of Step 1: Set up SAML in Single Sign‑On.

    The information depicted in this screenshot is described in the step above.

  7. Record the App Federation Metadata Url. You need this for setting up the SSO identity provider configurations. For more infomation, see Setting up SAML.

  8. Provide a Notification Email and click Save.

    The information depicted in this screenshot is described in the step above.

  9. Navigate to Users and groups tab and then click Add User .

    The information depicted in this screenshot is described in the step above.

  10. Select users or group names from the dropdown. For example, you can add a group that includes all users that should be able to log in to the Single Sign‑On plan.

    The information depicted in this screenshot is described in the step above.

Step 3: Set up Claims Mapping

  1. Navigate to Azure Active Directory > App registration. Click your app.

    The information depicted in this screenshot is described in the step above.

  2. To enable user attribute mappings, do the following:

    1. Select the View and edit all other user attributes checkbox under the User Attributes header.
    2. Modify the attributes.

    For more information, see How to: Customize claims issued in the SAML token for enterprise applications.

    The information depicted in this screenshot is described in the step above.

  3. To pass group membership claims to the app, do the following:

    1. Click Manifest.
    2. Locate groupMembershipClaims and set the value to one of the following:
      • SecurityGroup. Groups claim will contain identifiers of all security groups of which the user is a member.
      • All. Groups claim will contain the identifiers of all security groups and distribution lists of which the user is a member.
    3. Save the change.

    For more information, see How to: Customize claims issued in the SAML token for enterprise applications.

    The information depicted in this screenshot is described in the steps above.

  4. Navigate to Azure Active Directory > Groups.

  5. For each group that is used by the Single Sign‑On plan, record the Object ID. Azure AD passes the Object ID of these groups to the Single Sign‑On plan. For more information, see Configure Group Permissions.

    The information depicted in this screenshot is described in the steps above.