Povratne informacije Uredi

Tutorial: Configure AWS IAM Identity Center for automatic user provisioning

  • Članak
  • 6 min. za čitanje

This tutorial describes the steps you need to perform in both AWS IAM Identity Center(successor to AWS single sign-On) and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to AWS IAM Identity Center 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 AWS IAM Identity Center
  • Remove users in AWS IAM Identity Center when they no longer require access
  • Keep user attributes synchronized between Azure AD and AWS IAM Identity Center
  • Provision groups and group memberships in AWS IAM Identity Center
  • IAM Identity Center to AWS IAM Identity Center

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 SAML connection from your Azure AD account to AWS IAM Identity Center, as described in Tutorial

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 AWS IAM Identity Center.

Step 2. Configure AWS IAM Identity Center to support provisioning with Azure AD

  1. Open the AWS IAM Identity Center.

  2. Choose Settings in the left navigation pane

  3. In Settings, click on Enable in the Automatic provisioning section.

    Screenshot of enabling automatic provisioning.

  4. In the Inbound automatic provisioning dialog box, copy and save the SCIM endpoint and Access Token (visible after clicking on Show Token). These values will be entered in the Tenant URL and Secret Token field in the Provisioning tab of your AWS IAM Identity Center application in the Azure portal. Screenshot of extracting provisioning configurations.

Add AWS IAM Identity Center from the Azure AD application gallery to start managing provisioning to AWS IAM Identity Center. If you have previously setup AWS IAM Identity Center for SSO, you can use the same application. 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.

  • Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

  • If you need additional roles, you can update the application manifest to add new roles.

Step 5. Configure automatic user provisioning to AWS IAM Identity Center

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 AWS IAM Identity Center 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 AWS IAM Identity Center.

    Screenshot of the AWS IAM Identity Center 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 AWS IAM Identity Center Tenant URL and Secret Token retrieved earlier in Step 2. Click Test Connection to ensure Azure AD can connect to AWS IAM Identity Center.

    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 AWS IAM Identity Center.

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

    Attribute Type Supported for Filtering
    userName String ✓
    active Boolean
    displayName String
    title String
    emails[type eq "work"].value String
    preferredLanguage String
    name.givenName String
    name.familyName String
    name.formatted String
    addresses[type eq "work"].formatted String
    addresses[type eq "work"].streetAddress String
    addresses[type eq "work"].locality String
    addresses[type eq "work"].region String
    addresses[type eq "work"].postalCode String
    addresses[type eq "work"].country String
    phoneNumbers[type eq "work"].value String
    externalId String
    locale String
    timezone String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:division String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:organization String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager Reference

  10. Under the Mappings section, select Synchronize Azure Active Directory Groups to AWS IAM Identity Center.

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

    Attribute Type Supported for Filtering
    displayName String ✓
    externalId 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 AWS IAM Identity Center, 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 AWS IAM Identity Center 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:

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

Troubleshooting Tips

Missing attributes

When exporting a user to AWS, they are required to have the following attributes

  • firstName
  • lastName
  • displayName
  • userName

Users who don't have these attributes will fail with the following error

errorcode

Multi-valued attributes

AWS does not support the following multi-valued attributes:

  • email
  • phone numbers

Trying to flow the above as multi-valued attributes will result in the following error message

errorcode2

There are two ways to resolve this

  1. Ensure the user only has one value for phoneNumber/email
  2. Remove the duplicate attributes. For example, having two different attributes being mapped from Azure AD both mapped to "phoneNumber___" on the AWS side would result in the error if both attributes have values in Azure AD. Only having one attribute mapped to a "phoneNumber____ " attribute would resolve the error.

Invalid characters

Currently AWS IAM Identity Center is not allowing some other characters that Azure AD supports like tab (\t), new line (\n), return carriage (\r), and characters such as " <|>|;|:% ".

You can also check the AWS IAM Identity Center troubleshooting tips here for more troubleshooting tips

Additional resources

Next steps