Split (1)

train · 107k rows

id stringlengths 8 78	source stringclasses 743 values	chunk_id int64 1 5.05k	text stringlengths 593 49.7k
sso-ug-016	sso-ug.pdf	16	Platform • Conﬁgure SAML and SCIM with Microsoft Entra ID and IAM Identity Center • Conﬁgure SAML and SCIM with Okta and IAM Identity Center • Setting up SCIM provisioning between OneLogin and IAM Identity Center • Using Ping Identity products with IAM Identity Center • Conﬁgure user access with the default IAM Identity Center directory • Video tutorials 31 AWS IAM Identity Center User Guide Using Active Directory as an identity source If you are managing users in either your AWS Managed Microsoft AD directory using AWS Directory Service or your self-managed directory in Active Directory (AD), you can change your IAM Identity Center identity source to work with those users. We recommend that you consider connecting this identity source when you enable IAM Identity Center and choose your identity source. Doing this before you create any users and groups in the default Identity Center directory will help you avoid the additional conﬁguration that's required if you change your identity source later. To use Active Directory as your identity source, your conﬁguration must meet the following prerequisites: • If you're using AWS Managed Microsoft AD, you must enable IAM Identity Center in the same AWS Region where your AWS Managed Microsoft AD directory is set up. IAM Identity Center stores the assignment data in the same Region as the directory. To administer IAM Identity Center, you might need to switch to the Region where IAM Identity Center is conﬁgured. Also, note that the AWS access portal uses the same access URL as your directory. • Use an Active Directory residing in the management account: You must have an existing AD Connector or AWS Managed Microsoft AD directory set up in AWS Directory Service, and it must reside within your AWS Organizations management account. You can connect only one AD Connector directory or one directory in AWS Managed Microsoft AD at a time. If you need to support multiple domains or forests, use AWS Managed Microsoft AD. For more information, see: • Connect a directory in AWS Managed Microsoft AD to IAM Identity Center • Connect a self-managed directory in Active Directory to IAM Identity Center • Use an Active Directory residing in the delegated administrator account: If you plan to enable an IAM Identity Center delegated administrator and use Active Directory as your IAM Identity Center identity source, you can use an existing AD Connector or AWS Managed Microsoft AD directory set up in AWS Directory residing in the delegated admin account. If you decide to change the IAM Identity Center identity source from any other source to Active Directory, or change it from Active Directory to any other source, the directory must reside in (be owned by) the IAM Identity Center delegated administrator member account if one exists; otherwise, it must be in the management account. Active Directory 32 AWS IAM Identity Center User Guide This tutorial guides you through the basic set up for using Active Directory as an IAM Identity Center identity source. Step 1: Connect Active Directory and specify a user If you're already using Active Directory , the following topics will help you prepare to connect your directory to IAM Identity Center. Note If you plan to connect an AWS Managed Microsoft AD directory or a self-managed directory in Active Directory and you're not using RADIUS MFA with AWS Directory Service, enable MFA in IAM Identity Center. AWS Managed Microsoft AD 1. Review the guidance in Connect to a Microsoft AD directory. 2. Follow the steps in Connect a directory in AWS Managed Microsoft AD to IAM Identity Center. 3. Conﬁgure Active Directory to synchronize the user to whom you want to grant administrative permissions into IAM Identity Center. For more information, see Synchronize an administrative user into IAM Identity Center. Self-managed directory in Active Directory 1. Review the guidance in Connect to a Microsoft AD directory. 2. Follow the steps in Connect a self-managed directory in Active Directory to IAM Identity Center. 3. Conﬁgure Active Directory to synchronize the user to whom you want to grant administrative permissions into IAM Identity Center. For more information, see Synchronize an administrative user into IAM Identity Center. Step 2: Synchronize an administrative user into IAM Identity Center After you connect your directory to IAM Identity Center, you can specify a user to whom you want to grant administrative permissions, and then synchronize that user from your directory into IAM Identity Center. 1. Open the IAM Identity Center console. Active Directory 33 AWS IAM Identity Center 2. Choose Settings. User Guide 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. On the Manage Sync page, choose the Users tab, and then choose Add users and groups. 5. On the Users tab, under User, enter the exact username and
sso-ug-017	sso-ug.pdf	17	Center After you connect your directory to IAM Identity Center, you can specify a user to whom you want to grant administrative permissions, and then synchronize that user from your directory into IAM Identity Center. 1. Open the IAM Identity Center console. Active Directory 33 AWS IAM Identity Center 2. Choose Settings. User Guide 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. On the Manage Sync page, choose the Users tab, and then choose Add users and groups. 5. On the Users tab, under User, enter the exact username and choose Add. 6. Under Added Users and Groups, do the following: a. b. c. Conﬁrm that the user to whom you want to grant administrative permissions is speciﬁed. Select the check box to the left of the username. Choose Submit. 7. 8. In the Manage sync page, the user that you speciﬁed appears in the Users in sync scope list. In the navigation pane, choose Users. 9. On the Users page, it might take some time for the user that you speciﬁed to appear in the list. Choose the refresh icon to update the list of users. At this point, your user doesn't have access to the management account. You will set up administrative access to this account by creating an administrative permission set and assigning the user to that permission set. For more information, see Create a permission set. Setting up SCIM provisioning between CyberArk and IAM Identity Center IAM Identity Center supports automatic provisioning (synchronization) of user information from CyberArk Directory Platform into IAM Identity Center. This provisioning uses the System for Cross- domain Identity Management (SCIM) v2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. You conﬁgure this connection in CyberArk using your IAM Identity Center SCIM endpoint and access token. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in CyberArk to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and CyberArk. This guide is based on CyberArk as of August 2021. Steps for newer versions may vary. This guide contains a few notes regarding conﬁguration of user authentication through SAML. CyberArk 34 AWS IAM Identity Center Note User Guide Before you begin deploying SCIM, we recommend that you ﬁrst review the Considerations for using automatic provisioning. Then continue reviewing additional considerations in the next section. Topics • Prerequisites • SCIM considerations • Step 1: Enable provisioning in IAM Identity Center • Step 2: Conﬁgure provisioning in CyberArk • (Optional) Step 3: Conﬁgure user attributes in CyberArk for access control (ABAC) in IAM Identity Center • (Optional) Passing attributes for access control Prerequisites You will need the following before you can get started: • CyberArk subscription or free trial. To sign up for a free trial visit CyberArk. • An IAM Identity Center enabled account (free). For more information, see Enable IAM Identity Center. • A SAML connection from your CyberArk account to IAM Identity Center, as described in CyberArk documentation for IAM Identity Center. • Associate the IAM Identity Center connector with the roles, users and organizations you want to allow access to AWS accounts. SCIM considerations The following are considerations when using CyberArk federation for IAM Identity Center: • Only roles mapped in the application Provisioning section will be synchronized to IAM Identity Center. Prerequisites 35 AWS IAM Identity Center User Guide • The provisioning script is supported only in its default state, once changed the SCIM provisioning might fail. • Only one phone number attribute can be synchronized and the default is “work phone”. • If the role mapping in CyberArk IAM Identity Center application is changed, the below behavior is expected: • If the role names are changed - no changes to the group names in IAM Identity Center. • If the group names are changed - new groups will be created in IAM Identity Center, old groups will remain but will have no members. • User synchronization and de-provisioning behavior can be set up from the CyberArk IAM Identity Center application, make sure you set up the right behavior for your organization. These are the options you have: • Overwrite (or not) users in Identity Center directory with the same principal name. • De-provision users from IAM Identity Center when the user is removed from the CyberArk role. • De-provision user behavior - disable or delete. Step 1: Enable provisioning in IAM Identity Center In this ﬁrst step, you use the IAM Identity Center console to enable automatic provisioning. To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On
sso-ug-018	sso-ug.pdf	18	your organization. These are the options you have: • Overwrite (or not) users in Identity Center directory with the same principal name. • De-provision users from IAM Identity Center when the user is removed from the CyberArk role. • De-provision user behavior - disable or delete. Step 1: Enable provisioning in IAM Identity Center In this ﬁrst step, you use the IAM Identity Center console to enable automatic provisioning. To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Step 1: Enable provisioning in IAM Identity Center 36 AWS IAM Identity Center User Guide Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in your IdP later in this tutorial. 5. Choose Close. Now that you have set up provisioning in the IAM Identity Center console, you need to complete the remaining tasks using the CyberArk IAM Identity Center application. These steps are described in the following procedure. Step 2: Conﬁgure provisioning in CyberArk Use the following procedure in the CyberArk IAM Identity Center application to enable provisioning with IAM Identity Center. This procedure assumes that you have already added the CyberArk IAM Identity Center application to your CyberArk admin console under Web Apps. If you have not yet done so, refer to the Prerequisites, and then complete this procedure to conﬁgure SCIM provisioning. To conﬁgure provisioning in CyberArk 1. Open the CyberArk IAM Identity Center application that you added as part of conﬁguring SAML for CyberArk (Apps > Web App). See Prerequisites. 2. Choose the IAM Identity Center application and go to the Provisioning section. 3. Check the box for Enable provisioning for this application and choose Live Mode. 4. 5. 6. In the previous procedure, you copied the SCIM endpoint value from IAM Identity Center. Paste that value into the SCIM Service URL ﬁeld, in the CyberArk IAM Identity Center application set the Authorization Type to be Authorization Header. Set the Header Type to Bearer Token. From the previous procedure you copied the Access token value in IAM Identity Center. Paste that value into the Bearer Token ﬁeld in the CyberArk IAM Identity Center application. 7. Click Verify to test and apply the conﬁguration. Step 2: Conﬁgure provisioning in CyberArk 37 AWS IAM Identity Center User Guide 8. Under the Sync Options, choose the right behavior for which you want the outbound provisioning from CyberArk to work. You can choose to overwrite (or not) existing IAM Identity Center users with similar principal name, and the de-provisioning behavior. 9. Under Role Mapping set up the mapping from CyberArk roles, under the Name ﬁeld to the IAM Identity Center group, under the Destination Group. 10. Click Save at the bottom once you are done. 11. To verify that users have been successfully synchronized to IAM Identity Center, return to the IAM Identity Center console and choose Users. Synchronized users from CyberArk will appear on the Users page. These users can now be assigned to accounts and can connect within IAM Identity Center. (Optional) Step 3: Conﬁgure user attributes in CyberArk for access control (ABAC) in IAM Identity Center This is an optional procedure for CyberArk should you choose to conﬁgure attributes for IAM Identity Center to manage access to your AWS resources. The attributes that you deﬁne in CyberArk are passed in a SAML assertion to IAM Identity Center. You then create a permission set in IAM Identity Center to manage access based on the attributes you passed from CyberArk. Before you begin this procedure, you must ﬁrst enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. To conﬁgure user attributes in CyberArk for access control in IAM Identity Center 1. Open the CyberArk IAM Identity Center application that you installed as part of conﬁguring SAML for CyberArk (Apps > Web Apps). 2. Go to the SAML Response option. 3. Under Attributes, add the relevant attributes to the table following the below logic: a. Attribute Name is the original attribute name from CyberArk. b. Attribute Value is the attribute name sent
sso-ug-019	sso-ug.pdf	19	you must ﬁrst enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. To conﬁgure user attributes in CyberArk for access control in IAM Identity Center 1. Open the CyberArk IAM Identity Center application that you installed as part of conﬁguring SAML for CyberArk (Apps > Web Apps). 2. Go to the SAML Response option. 3. Under Attributes, add the relevant attributes to the table following the below logic: a. Attribute Name is the original attribute name from CyberArk. b. Attribute Value is the attribute name sent in the SAML assertion to IAM Identity Center. 4. Choose Save. (Optional) Step 3: Conﬁgure user attributes in CyberArk for access control (ABAC) in IAM Identity Center 38 AWS IAM Identity Center User Guide (Optional) Passing attributes for access control You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. Conﬁgure SAML and SCIM with Google Workspace and IAM Identity Center If your organization is using Google Workspace you can integrate your users from Google Workspace into IAM Identity Center to give them access to AWS resources. You can achieve this integration by changing your IAM Identity Center identity source from the default IAM Identity Center identity source to Google Workspace. User information from Google Workspace is synchronized into IAM Identity Center using the System for Cross-domain Identity Management (SCIM) 2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. You conﬁgure this connection in Google Workspace using your SCIM endpoint for IAM Identity Center and an IAM Identity Center bearer token. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in Google Workspace to the named attributes in IAM Identity Center. This mapping matches the expected user attributes between IAM Identity Center and Google Workspace. To do this, you need to set up Google Workspace as an identity provider and connect with your IAM Identity Center. (Optional) Passing attributes for access control 39 AWS IAM Identity Center Objective User Guide The steps in this tutorial help guide you through establishing the SAML connection between Google Workspace and AWS. Later, you will synchronize users from Google Workspace using SCIM. To verify everything is conﬁgured correctly, after completing the conﬁguration steps you will sign- in as a Google Workspace user and verify access to AWS resources. Note that this tutorial is based on a small Google Workspace directory test environment. Directory structures such as groups and organization units aren't included in this tutorial. After completing this tutorial, your users will be able to access the AWS access portal with your Google Workspace credentials. Note To sign up for a free trial of Google Workspace visit Google Workspace on Google's website. If you haven't enabled IAM Identity Center yet, see Enable IAM Identity Center. Considerations • Before you conﬁgure SCIM provisioning between Google Workspace and IAM Identity Center, we recommend that you ﬁrst review Considerations for using automatic provisioning. • SCIM automatic synchronization from Google Workspace is currently limited to user provisioning. Automatic group provisioning is not supported at this time. Groups can be manually created with AWS CLI Identity Store create-group command or AWS Identity and Access Management (IAM) API CreateGroup. Alternatively, you can use ssosync to synchronize Google Workspace users and groups into IAM Identity Center. • Every Google Workspace user must have a First name, Last name, Username and Display name value speciﬁed. • Each Google Workspace user has only a single value per data attribute, such as email address or phone number. Any users that have multiple values will fail to synchronize. If there are users that have multiple values in their attributes, remove the duplicate attributes before attempting to provision the user in IAM Identity Center. For example, only one phone number attribute can be synchronized, since the default phone number attribute is "work phone", use the "work phone" attribute to store the user's phone number, even if the phone number for the user is a home phone or a mobile phone. • Attributes are still synchronized if the user is disabled in IAM Identity Center, but still active in Google Workspace. Considerations 40
sso-ug-020	sso-ug.pdf	20	have multiple values will fail to synchronize. If there are users that have multiple values in their attributes, remove the duplicate attributes before attempting to provision the user in IAM Identity Center. For example, only one phone number attribute can be synchronized, since the default phone number attribute is "work phone", use the "work phone" attribute to store the user's phone number, even if the phone number for the user is a home phone or a mobile phone. • Attributes are still synchronized if the user is disabled in IAM Identity Center, but still active in Google Workspace. Considerations 40 AWS IAM Identity Center User Guide • If there is an existing user in Identity Center directory with the same username and email, the user will be overwritten and synchronized using SCIM from Google Workspace. • There are additional considerations when changing your identity source. For more information, see the section called “Changing from IAM Identity Center to an external IdP”. Step 1: Google Workspace: Conﬁgure the SAML application 1. 2. 3. 4. Sign in to your Google Admin console using an account with super administrator privileges. In the left navigation panel of your Google Admin console, choose Apps and then choose Web and Mobile Apps. In the Add app dropdown list, select Search for apps. In the search box enter Amazon Web Services, then select Amazon Web Services (SAML) app from the list. 5. On the Google Identity Provider details - Amazon Web Services page, you can do either of the following: a. Download IdP metadata. b. Copy the SSO URL, Entity ID URL, and Certiﬁcate information. You will need either the XML ﬁle or URL information in Step 2. 6. Before moving to the next step in the Google Admin console, leave this page open and move to the IAM Identity Center console. Step 2: IAM Identity Center and Google Workspace: Change the IAM Identity Center identity source and setup Google Workspace as an SAML identity provider 1. Sign in to the IAM Identity Center console using a role with administrative permissions. 2. Choose Settings in the left navigation pane. 3. On the Settings page, choose Actions, and then choose Change identity source. • If you haven't enabled IAM Identity Center, see Enable IAM Identity Center for more information. After enabling and accessing IAM Identity Center for the ﬁrst time, you will arrive at the Dashboard where you can select Choose your identity source. Step 1: Google Workspace: Conﬁgure the SAML application 41 AWS IAM Identity Center User Guide 4. On the Choose identity source page, select External identity provider, and then choose Next. 5. The Conﬁgure external identity provider page opens. To complete this page and the Google Workspace page in Step 1, you will need to complete the following: • Under Identity Provider metadata section in the IAM Identity Center console, you will need to do either of the following: i. ii. Upload the Google SAML metadata as the IdP SAML metadata in the IAM Identity Center console. Copy and paste the Google SSO URL into the IdP Sign-in URL ﬁeld, Google Issuer URL into the IdP issuer URL ﬁeld, and upload the Google Certiﬁcate as the IdP certiﬁcate. 6. After providing the Google metadata in the Identity Provider metadata section of the IAM Identity Center console, copy the IAM Identity Assertion Consumer Service (ACS) URL and IAM Identity Center issuer URL. You will need to provide these URLs in the Google Admin console in the next step. 7. Leave the page open with the IAM Identity Center console and return to the Google Admin console. You should be on the Amazon Web Services - Service Provider details page. Select Continue. 8. On the Service provider details page, enter the ACS URL and Entity ID values. You copied these values in the previous step and they can be found in the IAM Identity Center console. • Paste the IAM Identity Center Assertion Consumer Service (ACS) URL into the ACS URL ﬁeld • Paste the IAM Identity Center issuer URL into the Entity ID ﬁeld. 9. On the Service provider details page, complete the ﬁelds under Name ID as follows: • For Name ID format, select EMAIL • For Name ID, select Basic Information > Primary email 10. Choose Continue. 11. On the Attribute Mapping page, under Attributes, choose ADD MAPPING, and then conﬁgure these ﬁelds under Google Directory attribute: • For the https://aws.amazon.com/SAML/Attributes/RoleSessionName app attribute, select the ﬁeld Basic Information, Primary Email from the Google Directory attributes. Step 2: IAM Identity Center and Google Workspace: Change the IAM Identity Center identity source and setup Google Workspace as an SAML identity provider 42 AWS IAM Identity Center User Guide • For the https://aws.amazon.com/SAML/Attributes/Role app attribute, select any Google Directory attributes. A Google Directory attribute could be Department.
sso-ug-021	sso-ug.pdf	21	• For Name ID, select Basic Information > Primary email 10. Choose Continue. 11. On the Attribute Mapping page, under Attributes, choose ADD MAPPING, and then conﬁgure these ﬁelds under Google Directory attribute: • For the https://aws.amazon.com/SAML/Attributes/RoleSessionName app attribute, select the ﬁeld Basic Information, Primary Email from the Google Directory attributes. Step 2: IAM Identity Center and Google Workspace: Change the IAM Identity Center identity source and setup Google Workspace as an SAML identity provider 42 AWS IAM Identity Center User Guide • For the https://aws.amazon.com/SAML/Attributes/Role app attribute, select any Google Directory attributes. A Google Directory attribute could be Department. 12. Choose Finish 13. Return to the IAM Identity Center console and choose Next. On the Review and Conﬁrm page, review the information and then enter ACCEPT into the space provided. Choose Change identity source. You are now ready to enable the Amazon Web Services app in Google Workspace so that your users can be provisioned into IAM Identity Center. Step 3: Google Workspace: Enable the apps 1. Return to the Google Admin Console and your AWS IAM Identity Center application which can be found under Apps and Web and Mobile Apps. 2. In the User access panel next to User access, choose the down arrow to expand User access to display the Service status panel. 3. In Service status panel, choose ON for everyone, and then choose SAVE. Note To help maintain the principle of least privilege, we recommend that after you complete this tutorial you change the Service status to OFF for everyone. Only users that need access to AWS should have the service enabled. You can use Google Workspace groups or organizational units to give user access to a particular subset of your users. Step 4: IAM Identity Center: Set up IAM Identity Center automatic provisioning 1. Return to the IAM Identity Center console. 2. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. Step 3: Google Workspace: Enable the apps 43 AWS IAM Identity Center User Guide 3. In the Inbound automatic provisioning dialog box, copy each of the values for the following options. In Step 5 of this tutorial, you will enter these values to conﬁgure automatic provisioning in Google Workspace. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. 4. Choose Close. Now that you've set up provisioning in the IAM Identity Center console, in the next step you will conﬁgure auto provisioning in Google Workspace. Step 5: Google Workspace: Conﬁgure auto provisioning 1. Return to the Google Admin console and your AWS IAM Identity Center application which can be found under Apps and Web and Mobile apps. In the Auto provisioning section, choose Conﬁgure auto provisioning. 2. In the previous procedure, you copied the Access token value in IAM Identity Center console. Paste that value into the Access token ﬁeld and choose Continue. Also, in the previous procedure, you copied the SCIM endpoint value in IAM Identity Center console. Paste that value into the Endpoint URL ﬁeld and choose Continue. 3. Verify that all mandatory IAM Identity Center attributes (those marked with *) are mapped to Google Cloud Directory attributes. If not, choose the down arrow and map to the appropriate attribute. Choose Continue. 4. 5. In Provisioning scope section, you can choose a group with your Google Workspace directory to provide access to the Amazon Web Services app. Skip this step and select Continue. In Deprovisioning section, you can choose how to respond to diﬀerent events that remove access from a user. For each situation you can specify the amount of time before deprovisioning begins to: Step 5: Google Workspace: Conﬁgure auto provisioning 44 AWS IAM Identity Center User Guide • within 24 hours • after one day • after seven days • after 30 days Each situation has a time setting for when to suspend an account's access and when to delete the account. Tip Always set more time before deleting a user's account than for suspending a user's account. 6. Choose Finish. You are returned to the Amazon Web Services app page. 7. In the Auto-provisioning section, turn on the toggle switch to change it from Inactive to Active. Note The activation slider is disabled if IAM Identity Center isn’t turned on for users. Choose User access and turn the app on to enable the slider. 8. 9. In the conﬁrmation dialog box, choose Turn on. To verify that users are successfully synchronized to IAM Identity Center, return to the IAM Identity
sso-ug-022	sso-ug.pdf	22	account. Tip Always set more time before deleting a user's account than for suspending a user's account. 6. Choose Finish. You are returned to the Amazon Web Services app page. 7. In the Auto-provisioning section, turn on the toggle switch to change it from Inactive to Active. Note The activation slider is disabled if IAM Identity Center isn’t turned on for users. Choose User access and turn the app on to enable the slider. 8. 9. In the conﬁrmation dialog box, choose Turn on. To verify that users are successfully synchronized to IAM Identity Center, return to the IAM Identity Center console and choose Users. The Users page lists the users from your Google Workspace directory that were created by SCIM. If users aren't listed yet, it might be that provisioning is still in process. Provisioning can take up to 24 hours, although in most cases it completes within minutes. Make sure to refresh the browser window every few minutes. Select a user and view their details. The information should match the information in the Google Workspace directory. Step 5: Google Workspace: Conﬁgure auto provisioning 45 AWS IAM Identity Center User Guide Congratulations! You have successfully set up a SAML connection between Google Workspace and AWS and have veriﬁed that automatic provisioning is working. You can now assign these users to accounts and applications in IAM Identity Center. For this tutorial, in the next step let's designate one of the users as the IAM Identity Center administrator by granting them administrative permissions to the management account. Passing attributes for access control - Optional You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. Assign access to AWS accounts The following steps are only required to grant access to AWS accounts only. These steps are not required to grant access to AWS applications. Note To complete this step, you'll need an Organization instance of IAM Identity Center. For more information, see Organization and account instances of IAM Identity Center. Passing attributes for access control - Optional 46 AWS IAM Identity Center User Guide Step 1: IAM Identity Center: Grant Google Workspace users access to accounts 1. Return to the IAM Identity Center console. In the IAM Identity Center navigation pane, under Multi-account permissions, choose AWS accounts. 2. On the AWS accounts page the Organizational structure displays your organizational root with your accounts underneath it in the hierarchy. Select the checkbox for your management account, then select Assign users or groups. 3. The Assign users and groups workﬂow displays. It consists of three steps: a. b. For Step 1: Select users and groups choose the user that will be performing the administrator job function. Then choose Next. For Step 2: Select permission sets choose Create permission set to open a new tab that steps you through the three sub-steps involved in creating a permission set. i. For Step 1: Select permission set type complete the following: • In Permission set type, choose Predeﬁned permission set. • In Policy for predeﬁned permission set, choose AdministratorAccess. Choose Next. ii. For Step 2: Specify permission set details, keep the default settings, and choose Next. The default settings create a permission set named AdministratorAccess with session duration set to one hour. iii. For Step 3: Review and create, verify that the Permission set type uses the AWS managed policy AdministratorAccess. Choose Create. On the Permission sets page a notiﬁcation appears informing you that the permission set was created. You can close this tab in your web browser now. iv. On the Assign users and groups browser tab, you are still on Step 2: Select permission sets from which you started the create permission set workﬂow. v. In the Permissions sets area, choose the Refresh button. The AdministratorAccess permission set you created appears in the list. Select the checkbox for that permission set and then choose Next. c. For Step 3: Review and submit review the selected user and permission set, then choose Submit. Assign access to AWS accounts 47 AWS IAM Identity Center User Guide The page updates with a message that your AWS account is being conﬁgured. Wait until the process completes. You are returned to the AWS accounts page. A notiﬁcation
sso-ug-023	sso-ug.pdf	23	Select permission sets from which you started the create permission set workﬂow. v. In the Permissions sets area, choose the Refresh button. The AdministratorAccess permission set you created appears in the list. Select the checkbox for that permission set and then choose Next. c. For Step 3: Review and submit review the selected user and permission set, then choose Submit. Assign access to AWS accounts 47 AWS IAM Identity Center User Guide The page updates with a message that your AWS account is being conﬁgured. Wait until the process completes. You are returned to the AWS accounts page. A notiﬁcation message informs you that your AWS account has been reprovisioned and the updated permission set applied. When the user sign in they will have the option of choosing the AdministratorAccess role. Note SCIM automatic synchronization from Google Workspace only supports provisioning users. Automatic group provisioning is not supported at this time. You can't create groups for your Google Workspace users using the AWS Management Console. After provisioning users, you can create groups using AWS CLI Identity Store create-group command or IAM API CreateGroup. Step 2: Google Workspace: Conﬁrm Google Workspace users access to AWS resources 1. Sign in to Google using a test user account. To learn how to add users to Google Workspace, 2. 3. 4. see Google Workspace documentation. Select the Google apps launcher (waﬄe) icon. Scroll to the bottom of the apps list where your custom Google Workspace apps are located. The Amazon Web Services app is displayed. Select the Amazon Web Services app. You are signed into the AWS access portal and can see the AWS account icon. Expand that icon to see the list of AWS accounts that the user can access. In this tutorial you only worked with a single account, so expanding the icon only shows one account. 5. Select the account to display the permission sets available to the user. In this tutorial you created the AdministratorAccess permission set. 6. Next to the permission set are links for the type of access available for that permission set. When you created the permission set, you speciﬁed both management console and programmatic access be enabled, so those two options are present. Select Management console to open the AWS Management Console. 7. The user is signed in to the console. Assign access to AWS accounts 48 AWS IAM Identity Center Next steps User Guide Now that you've conﬁgured Google Workspace as an identity provider and provisioned users in IAM Identity Center, you can: • Use the AWS CLI Identity Store create-group command or IAM API CreateGroup to create groups for your users. Groups are useful when assigning access to AWS accounts and applications. Rather than assign each user individually, you give permissions to a group. Later, as you add or remove users from a group, the user dynamically gets or loses access to accounts and applications that you assigned to the group. • Conﬁgure permissions based on job functions, see Create a permission sets. Permission sets deﬁne the level of access that users and groups have to an AWS account. Permission sets are stored in IAM Identity Center and can be provisioned to one or more AWS accounts. You can assign more than one permission set to a user. Note As an IAM Identity Center administrator, you'll occasionally need to replace older IdP certiﬁcates with newer ones. For example, you might need to replace an IdP certiﬁcate when the expiration date on the certiﬁcate approaches. The process of replacing an older certiﬁcate with a newer one is referred to as certiﬁcate rotation. Make sure to review how to manage the SAML certiﬁcates for Google Workspace. Troubleshooting For general SCIM and SAML troubleshooting with Google Workspace, see the following sections: • Speciﬁc users fail to synchronize into IAM Identity Center from an external SCIM provider • Issues regarding contents of SAML assertions created by IAM Identity Center • Duplicate user or group error when provisioning users or groups with an external identity provider • For Google Workspace troubleshooting, see Google Workspace documentation. Next steps 49 AWS IAM Identity Center User Guide The following resources can help you troubleshoot as you work with AWS: • AWS re:Post - Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support Using IAM Identity Center to connect with your JumpCloud Directory Platform IAM Identity Center supports automatic provisioning (synchronization) of user information from JumpCloud Directory Platform into IAM Identity Center. This provisioning uses the Security Assertion Markup Language (SAML) 2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. You conﬁgure this connection in JumpCloud using your IAM Identity Center SCIM endpoint and access token. When you conﬁgure SCIM synchronization, you create a mapping of
sso-ug-024	sso-ug.pdf	24	- Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support Using IAM Identity Center to connect with your JumpCloud Directory Platform IAM Identity Center supports automatic provisioning (synchronization) of user information from JumpCloud Directory Platform into IAM Identity Center. This provisioning uses the Security Assertion Markup Language (SAML) 2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. You conﬁgure this connection in JumpCloud using your IAM Identity Center SCIM endpoint and access token. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in JumpCloud to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and JumpCloud. This guide is based on JumpCloud as of June 2021. Steps for newer versions may vary. This guide contains a few notes regarding conﬁguration of user authentication through SAML. The following steps walk you through how to enable automatic provisioning of users and groups from JumpCloud to IAM Identity Center using the SCIM protocol. Note Before you begin deploying SCIM, we recommend that you ﬁrst review the Considerations for using automatic provisioning. Then continue reviewing additional considerations in the next section. Topics • Prerequisites • SCIM considerations • Step 1: Enable provisioning in IAM Identity Center • Step 2: Conﬁgure provisioning in JumpCloud JumpCloud 50 AWS IAM Identity Center User Guide • (Optional) Step 3: Conﬁgure user attributes in JumpCloud for access control in IAM Identity Center • (Optional) Passing attributes for access control Prerequisites You will need the following before you can get started: • JumpCloud subscription or free trial. To sign up for a free trial visit JumpCloud. • An IAM Identity Center enabled account (free). For more information, see Enable IAM Identity Center. • A SAML connection from your JumpCloud account to IAM Identity Center, as described in JumpCloud documentation for IAM Identity Center . • Associate the IAM Identity Center connector with the groups you want to allow access to AWS accounts. SCIM considerations The following are considerations when using JumpCloud federation for IAM Identity Center. • Only groups associated with the AWS Single Sign-On connector in JumpCloud will be synchronized with SCIM. • Only one phone number attribute can be synchronized and the default is "work phone." • Users in JumpCloud directory must have ﬁrst and last names conﬁgured to be synchronized to IAM Identity Center with SCIM. • Attributes are still synchronized if the user is disabled in IAM Identity Center but still activate in JumpCloud. • You can choose to enable SCIM sync for only user information by unchecking the "Enable management of User Groups and Group membership" in the connector. Step 1: Enable provisioning in IAM Identity Center In this ﬁrst step, you use the IAM Identity Center console to enable automatic provisioning. Prerequisites 51 AWS IAM Identity Center User Guide To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in your IdP later in this tutorial. 5. Choose Close. Now that you have set up provisioning in the IAM Identity Center console, you need to complete the remaining tasks using the JumpCloud IAM Identity Center connector. These steps are described in the following procedure. Step 2: Conﬁgure provisioning in JumpCloud Use the following procedure in the JumpCloud IAM Identity Center connector to enable provisioning with IAM Identity Center. This procedure assumes that you have already added the JumpCloud IAM Identity Center connector to your JumpCloud admin portal and groups. If you have not yet done so, refer to Prerequisites, and then complete this procedure to conﬁgure SCIM provisioning. Step 2: Conﬁgure provisioning in JumpCloud 52 AWS IAM Identity Center User Guide To conﬁgure provisioning in JumpCloud 1. Open the JumpCloud IAM Identity Center connector that you installed as part of conﬁguring SAML for JumpCloud (User Authentication > IAM Identity Center). See Prerequisites. 2. Choose the IAM Identity Center connector, and then choose the third tab Identity Management. 3. Check the
sso-ug-025	sso-ug.pdf	25	assumes that you have already added the JumpCloud IAM Identity Center connector to your JumpCloud admin portal and groups. If you have not yet done so, refer to Prerequisites, and then complete this procedure to conﬁgure SCIM provisioning. Step 2: Conﬁgure provisioning in JumpCloud 52 AWS IAM Identity Center User Guide To conﬁgure provisioning in JumpCloud 1. Open the JumpCloud IAM Identity Center connector that you installed as part of conﬁguring SAML for JumpCloud (User Authentication > IAM Identity Center). See Prerequisites. 2. Choose the IAM Identity Center connector, and then choose the third tab Identity Management. 3. Check the box for Enable management of User Groups and Group membership in this application if you want groups to SCIM sync. 4. Click on Conﬁgure. 5. 6. In the previous procedure, you copied the SCIM endpoint value in IAM Identity Center. Paste that value into the Base URL ﬁeld in the JumpCloud IAM Identity Center connector. From the previous procedure you copied the Access token value in IAM Identity Center. Paste that value into the Token Key ﬁeld in the JumpCloud IAM Identity Center connector. 7. Click Activate to apply the conﬁguration. 8. Make sure you have a green indicator next to Single Sign-On activated. 9. Move to the fourth tab User Groups and check the groups you want to be provisioned with SCIM. 10. Click Save at the bottom once you are done. 11. To verify that users have been successfully synchronized to IAM Identity Center, return to the IAM Identity Center console and choose Users. Synchronized users from JumpCloud appear on the Users page. These users can now be assigned to accounts within IAM Identity Center. (Optional) Step 3: Conﬁgure user attributes in JumpCloud for access control in IAM Identity Center This is an optional procedure for JumpCloud should you choose to conﬁgure attributes for IAM Identity Center to manage access to your AWS resources. The attributes that you deﬁne in JumpCloud are passed in a SAML assertion to IAM Identity Center. You then create a permission set in IAM Identity Center to manage access based on the attributes you passed from JumpCloud. Before you begin this procedure, you must ﬁrst enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. (Optional) Step 3: Conﬁgure user attributes in JumpCloud for access control in IAM Identity Center 53 AWS IAM Identity Center User Guide To conﬁgure user attributes in JumpCloud for access control in IAM Identity Center 1. Open the JumpCloud IAM Identity Center connector that you installed as part of conﬁguring SAML for JumpCloud (User Authentication > IAM Identity Center). 2. Choose the IAM Identity Center connector. Then, choose the second tab IAM Identity Center. 3. At the bottom of this tab you have User Attribute Mapping, choose Add new attribute, and then do the following: You must perform these steps for each attribute you will add for use in IAM Identity Center for access control. a. In the Service Provide Attribute Name ﬁeld, enter https://aws.amazon.com/SAML/ Attributes/AccessControl:AttributeName. Replace AttributeName with the name of the attribute you are expecting in IAM Identity Center. For example, https:// aws.amazon.com/SAML/Attributes/AccessControl:Email. b. In the JumpCloud Attribute Name ﬁeld, choose user attributes from your JumpCloud directory. For example, Email (Work). 4. Choose Save. (Optional) Passing attributes for access control You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. (Optional) Passing attributes for access control 54 AWS IAM Identity Center User Guide Conﬁgure SAML and SCIM with Microsoft Entra ID and IAM Identity Center AWS IAM Identity Center supports integration with Security Assertion Markup Language (SAML) 2.0 as well as automatic provisioning (synchronization) of user and group information from Microsoft Entra ID (formerly known as Azure Active Directory or Azure AD) into IAM Identity Center using the System for Cross-domain Identity Management (SCIM) 2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. Objective In this tutorial, you will set up a test lab and conﬁgure a SAML connection and SCIM provisioning between Microsoft Entra ID and IAM Identity Center. During the initial preparation steps, you'll create a test user (Nikki Wolf) in
sso-ug-026	sso-ug.pdf	26	integration with Security Assertion Markup Language (SAML) 2.0 as well as automatic provisioning (synchronization) of user and group information from Microsoft Entra ID (formerly known as Azure Active Directory or Azure AD) into IAM Identity Center using the System for Cross-domain Identity Management (SCIM) 2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. Objective In this tutorial, you will set up a test lab and conﬁgure a SAML connection and SCIM provisioning between Microsoft Entra ID and IAM Identity Center. During the initial preparation steps, you'll create a test user (Nikki Wolf) in both Microsoft Entra ID and IAM Identity Center which you'll use to test the SAML connection in both directions. Later, as part of the SCIM steps, you'll create a diﬀerent test user (Richard Roe) to verify that new attributes in Microsoft Entra ID are synchronizing to IAM Identity Center as expected. Prerequisites Before you can get started with this tutorial, you'll ﬁrst need to set up the following: • A Microsoft Entra ID tenant. For more information, see Quickstart: Set up a tenant in Microsoft documentation. • An AWS IAM Identity Center-enabled account. For more information, see Enable IAM Identity Center in the AWS IAM Identity Center User Guide. Considerations The following are important considerations about Microsoft Entra ID that can aﬀect how you plan to implement automatic provisioning with IAM Identity Center in your production environment using the SCIM v2 protocol. Automatic Provisioning Before you begin deploying SCIM, we recommend that you ﬁrst review Considerations for using automatic provisioning. Attributes for access control Microsoft Entra ID 55 AWS IAM Identity Center User Guide Attributes for access control is used in permission policies that determine who in your identity source can access your AWS resources. If an attribute is removed from a user in Microsoft Entra ID, that attribute will not be removed from the corresponding user in IAM Identity Center. This is a known limitation in Microsoft Entra ID. If an attribute is changed to a diﬀerent (non-empty) value on a user, that change will be synchronized to IAM Identity Center. Nested Groups The Microsoft Entra ID user provisioning service can't read or provision users in nested groups. Only users that are immediate members of an explicitly assigned group can be read and provisioned. Microsoft Entra ID doesn't recursively unpack the group memberships of indirectly assigned users or groups (users or groups that are members of a group that is directly assigned). For more information, see Assignment-based scoping in the Microsoft documentation. Alternatively, you can use IAM Identity Center conﬁgurable AD sync to integrate Active Directory groups with IAM Identity Center. Dynamic Groups The Microsoft Entra ID user provisioning service can read and provision users in dynamic groups. See below for an example showing the users and groups structure while using dynamic groups and how they are displayed in IAM Identity Center. These users and groups were provisioned from Microsoft Entra ID into IAM Identity Center via SCIM For example, if Microsoft Entra ID structure for dynamic groups is as follows: 1. Group A with members ua1, ua2 2. Group B with members ub1 3. Group C with members uc1 4. Group K with a rule to include members of Group A, B, C 5. Group L with a rule to include members Group B and C After the user and group information is provisioned from Microsoft Entra ID into IAM Identity Center through SCIM, the structure will be as follows: 1. Group A with members ua1, ua2 2. Group B with members ub1 3. Group C with members uc1 Considerations 56 AWS IAM Identity Center User Guide 4. Group K with members ua1, ua2, ub1, uc1 5. Group L with members ub1, uc1 When you conﬁgure automatic provisioning using dynamic groups, keep the following considerations in mind. • A dynamic group can include a nested group. However, Microsoft Entra ID provisioning service doesn’t ﬂatten the nested group. For example, if you have the following Microsoft Entra ID structure for dynamic groups: • Group A is a parent of group B. • Group A has ua1 as a member. • Group B has ub1 as a member. The dynamic group that includes Group A will only include the direct members of group A (that is, ua1). It won’t recursively include members of group B. • Dynamic groups can’t contain other dynamic groups. For more information, see Preview limitations in the Microsoft documentation. Step 1: Prepare your Microsoft tenant In this step, you will walk through how to install and conﬁgure your AWS IAM Identity Center enterprise application and assign access to a newly created Microsoft Entra ID test user. Step 1.1 > Step 1.1: Set up the AWS IAM Identity Center enterprise application in Microsoft Entra ID In this
sso-ug-027	sso-ug.pdf	27	group that includes Group A will only include the direct members of group A (that is, ua1). It won’t recursively include members of group B. • Dynamic groups can’t contain other dynamic groups. For more information, see Preview limitations in the Microsoft documentation. Step 1: Prepare your Microsoft tenant In this step, you will walk through how to install and conﬁgure your AWS IAM Identity Center enterprise application and assign access to a newly created Microsoft Entra ID test user. Step 1.1 > Step 1.1: Set up the AWS IAM Identity Center enterprise application in Microsoft Entra ID In this procedure, you install the AWS IAM Identity Center enterprise application in Microsoft Entra ID. You will need this application later to conﬁgure your SAML connection with AWS. 1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator. 2. Navigate to Identity > Applications > Enterprise applications, and then choose New application. 3. On the Browse Microsoft Entra Gallery page, enter AWS IAM Identity Center in the search box. Step 1: Prepare your Microsoft tenant 57 AWS IAM Identity Center User Guide 4. Select AWS IAM Identity Center from the results. 5. Choose Create. Step 1.2 > Step 1.2: Create a test user in Microsoft Entra ID Nikki Wolf is the name of your Microsoft Entra ID test user that you will create in this procedure. 1. 2. 3. 4. 5. In the Microsoft Entra admin center console, navigate to Identity > Users > All users. Select New user, and then choose Create new user at the top of the screen. In User principal name, enter NikkiWolf, and then select your preferred domain and extension. For example, [email protected]. In Display name, enter NikkiWolf. In Password, enter a strong password or select the eye icon to show the password that was auto-generated, and either copy or write down the value that's displayed. 6. Choose Properties, in First name, enter Nikki. In Last name, enter Wolf. 7. Choose Review + create, and then choose Create. Step 1.3 Step 1.3: Test Nikki's experience prior to assigning her permissions to AWS IAM Identity Center In this procedure, you will verify what Nikki can successfully sign into her Microsoft My Account portal. 1. In the same browser, open a new tab, go to the My Account portal sign-in page, and enter Nikki's full email address. For example, [email protected]. 2. When prompted, enter Nikki's password, and then choose Sign in. If this was an auto- generated password, you will be prompted to change the password. 3. On the Action Required page, choose Ask later to bypass the prompt for additional security methods. 4. On the My account page, in the left navigation pane, choose My Apps. Notice that besides Add-ins, no apps are displayed at this time. You'll add an AWS IAM Identity Center app that will appear here in a later step. Step 1: Prepare your Microsoft tenant 58 AWS IAM Identity Center Step 1.4 User Guide Step 1.4: Assign permissions to Nikki in Microsoft Entra ID Now that you have veriﬁed that Nikki can successfully access the My account portal, use this procedure to assign her user to the AWS IAM Identity Center app. 1. In the Microsoft Entra admin center console, navigate to Identity > Applications > Enterprise applications and then choose AWS IAM Identity Center from the list. 2. On the left, choose Users and groups. 3. Choose Add user/group. You can ignore the message stating that groups are not available for assignment. This tutorial does not use groups for assignments. 4. On the Add Assignment page, under Users, choose None Selected. 5. Select NikkiWolf, and then choose Select. 6. On the Add Assignment page, choose Assign. NikkiWolf now appears in the list of users who are assigned to the AWS IAM Identity Center app. Step 2: Prepare your AWS account In this step, you'll walk through how to use IAM Identity Center to conﬁgure access permissions (via permission set), manually create a corresponding Nikki Wolf user, and assign her the necessary permissions to administer resources in AWS. Step 2.1 > Step 2.1: Create a RegionalAdmin permission set in IAM Identity Center This permission set will be used to grant Nikki the necessary AWS account permissions required to manage Regions from the Account page within the AWS Management Console. All other permissions to view or manage any other information for Nikki's account is denied by default. 1. Open the IAM Identity Center console. 2. Under Multi-account permissions, choose Permission sets. 3. Choose Create permission set. 4. On the Select permission set type page, select Custom permission set, and then choose Next. Step 2: Prepare your AWS account 59 AWS IAM Identity Center User Guide 5. Select Inline policy to expand it, and then create a policy for
sso-ug-028	sso-ug.pdf	28	used to grant Nikki the necessary AWS account permissions required to manage Regions from the Account page within the AWS Management Console. All other permissions to view or manage any other information for Nikki's account is denied by default. 1. Open the IAM Identity Center console. 2. Under Multi-account permissions, choose Permission sets. 3. Choose Create permission set. 4. On the Select permission set type page, select Custom permission set, and then choose Next. Step 2: Prepare your AWS account 59 AWS IAM Identity Center User Guide 5. Select Inline policy to expand it, and then create a policy for the permission set using the following steps: a. Choose Add new statement to create a policy statement. b. Under Edit statement, select Account from the list, and then choose the following checkboxes. • ListRegions • GetRegionOptStatus • DisableRegion • EnableRegion c. Next to Add a resource, choose Add. d. On the Add resource page, under Resource type, select All Resources, and then choose Add resource. Verify that your policy looks like the following: { "Statement": [ { "Sid": "Statement1", "Effect": "Allow", "Action": [ "account:ListRegions", "account:DisableRegion", "account:EnableRegion", "account:GetRegionOptStatus" ], "Resource": [ "*" ] } ] } 6. Choose Next. 7. On the Specify permission set details page, under Permission set name, enter RegionalAdmin, and then choose Next. 8. On the Review and create page, choose Create. You should see RegionalAdmin displayed in the list of permission sets. Step 2: Prepare your AWS account 60 AWS IAM Identity Center Step 2.2 > User Guide Step 2.2: Create a corresponding NikkiWolf user in IAM Identity Center Since the SAML protocol does not provide a mechanism to query the IdP (Microsoft Entra ID) and automatically create users here in IAM Identity Center, use the following procedure to manually create a user in IAM Identity Center that mirrors the core attributes from Nikki Wolfs user in Microsoft Entra ID. 1. Open the IAM Identity Center console. 2. Choose Users, choose Add user, and then provide the following information: a. For both Username and Email address – Enter the same [email protected] that you used when creating your Microsoft Entra ID user. For example, [email protected]. b. Conﬁrm email address – Re-enter the email address from the previous step c. d. First name – Enter Nikki Last name – Enter Wolf e. Display name – Enter Nikki Wolf 3. Choose Next twice, then choose Add user. 4. Select Close. Step 2.3 Step 2.3: Assign Nikki to the RegionalAdmin permission set in IAM Identity Center Here you locate the AWS account in which Nikki will administer Regions, and then assign the necessary permissions required for her to successfully access the AWS access portal. 1. Open the IAM Identity Center console. 2. Under Multi-account permissions, choose AWS accounts. 3. Select the checkbox next to the account name (for example, Sandbox) where you want to grant Nikki access to manage Regions, and then choose Assign users and groups. 4. On the Assign users and groups page, choose the Users tab, ﬁnd and check the box next to Nikki, and then choose Next. 5. Step 2: Prepare your AWS account 61 AWS IAM Identity Center Example User Guide <caption>On the Select permission sets page, choose the RegionalAdmin permission set created in Step 2.1, and then choose Next.</caption> 6. On the Review and submit page, review your selections and then choose Submit. Step 3: Conﬁgure and test your SAML connection In this step, you conﬁgure your SAML connection using the AWS IAM Identity Center enterprise application in Microsoft Entra ID together with the external IdP settings in IAM Identity Center. Step 3.1 > Step 3.1: Collect required service provider metadata from IAM Identity Center In this step, you will launch the Change identity source wizard from within the IAM Identity Center console and retrieve the metadata ﬁle and the AWS speciﬁc sign-in URL you'll need to enter when conﬁguring the connection with Microsoft Entra ID in the next step. 1. In the IAM Identity Center console, choose Settings. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Change identity source. 3. On the Choose identity source page, select External identity provider, and then choose Next. 4. On the Conﬁgure external identity provider page, under Service provider metadata, choose Download metadata ﬁle to download the XML ﬁle. 5. 6. In the same section, locate the AWS access portal sign-in URL value and copy it. You will need to enter this value when prompted in the next step. Leave this page open, and move to the next step (Step 3.2) to conﬁgure the AWS IAM Identity Center enterprise application in Microsoft Entra ID. Later, you'll return to this page to complete the process. Step 3.2 > Step 3.2: Conﬁgure the AWS IAM Identity Center enterprise application in Microsoft Entra
sso-ug-029	sso-ug.pdf	29	the Conﬁgure external identity provider page, under Service provider metadata, choose Download metadata ﬁle to download the XML ﬁle. 5. 6. In the same section, locate the AWS access portal sign-in URL value and copy it. You will need to enter this value when prompted in the next step. Leave this page open, and move to the next step (Step 3.2) to conﬁgure the AWS IAM Identity Center enterprise application in Microsoft Entra ID. Later, you'll return to this page to complete the process. Step 3.2 > Step 3.2: Conﬁgure the AWS IAM Identity Center enterprise application in Microsoft Entra ID Step 3: Conﬁgure and test your SAML connection 62 AWS IAM Identity Center User Guide This procedure establishes one-half of the SAML connection on the Microsoft side using the values from the metadata ﬁle and Sign-On URL you obtained in the last step. 1. In the Microsoft Entra admin center console, navigate to Identity > Applications > Enterprise applications and then choose AWS IAM Identity Center. 2. On the left, choose 2. Set up Single sign-on. 3. On the Set up Single Sign-On with SAML page, choose SAML. Then choose Upload metadata ﬁle, choose the folder icon, select the service provider metadata ﬁle that you downloaded in the previous step, and then choose Add. 4. On the Basic SAML Conﬁguration page, verify that both the Identiﬁer and Reply URL values now point to endpoints in AWS that start with https://<REGION>.signin.aws.amazon.com/platform/saml/. 5. Under Sign on URL (Optional), paste in the AWS access portal sign-in URL value you copied in the previous step (Step 3.1), choose Save, and then choose X to close the window. 6. If prompted to test single sign-on with AWS IAM Identity Center, choose No I'll test later. You will do this veriﬁcation in a later step. 7. On the Set up Single Sign-On with SAML page, in the SAML Certiﬁcates section, next to Federation Metadata XML, choose Download to save the metadata ﬁle to your system. You will need to upload this ﬁle when prompted in the next step. Step 3.3 > Step 3.3: Conﬁgure the Microsoft Entra ID external IdP in AWS IAM Identity Center Here you will return to the Change identity source wizard in the IAM Identity Center console to complete the second-half of the SAML connection in AWS. 1. Return to the browser session you left open from Step 3.1 in the IAM Identity Center console. 2. On the Conﬁgure external identity provider page, in the Identity provider metadata section, under IdP SAML metadata, choose the Choose ﬁle button, and select the identity provider metadata ﬁle that you downloaded from Microsoft Entra ID in the previous step, and then choose Open. 3. Choose Next. 4. After you read the disclaimer and are ready to proceed, enter ACCEPT. Step 3: Conﬁgure and test your SAML connection 63 AWS IAM Identity Center User Guide 5. Choose Change identity source to apply your changes. Step 3.4 > Step 3.4: Test that Nikki is redirected to the AWS access portal In this procedure, you will test the SAML connection by signing in to Microsoft's My Account portal with Nikki's credentials. Once authenticated, you'll select the AWS IAM Identity Center application which will redirect Nikki to the AWS access portal. 1. Go to the My Account portal sign in page, and enter Nikki's full email address. For example, [email protected]. 2. When prompted, enter Nikki's password, and then choose Sign in. 3. On the My account page, in the left navigation pane, choose My Apps. 4. On the My Apps page, select the app named AWS IAM Identity Center. This should prompt you for additional authentication. 5. On Microsoft's sign in page, choose your NikkiWolf credentials. If prompted a second time for authentication, choose your NikkiWolf credentials again. This should automatically redirect you to the AWS access portal. Tip If you are not redirected successfully, check to make sure the AWS access portal sign-in URL value you entered in Step 3.2 matches the value you copied from Step 3.1. 6. Verify that your AWS accounts display. Tip If the page is empty and no AWS accounts display, conﬁrm that Nikki was successfully assigned to the RegionalAdmin permission set (see Step 2.3). Step 3.5 Step 3.5: Test Nikki's level of access to manage her AWS account Step 3: Conﬁgure and test your SAML connection 64 AWS IAM Identity Center User Guide In this step, you will check to determine Nikki's level of access to manage the Region settings for her AWS account. Nikki should only have suﬃcient administrator privileges to manage Regions from the Accounts page. 1. In the AWS access portal, choose the Accounts tab to display the list of accounts. The account names, account IDs, and email addresses associated with any accounts where you've deﬁned permission sets
sso-ug-030	sso-ug.pdf	30	(see Step 2.3). Step 3.5 Step 3.5: Test Nikki's level of access to manage her AWS account Step 3: Conﬁgure and test your SAML connection 64 AWS IAM Identity Center User Guide In this step, you will check to determine Nikki's level of access to manage the Region settings for her AWS account. Nikki should only have suﬃcient administrator privileges to manage Regions from the Accounts page. 1. In the AWS access portal, choose the Accounts tab to display the list of accounts. The account names, account IDs, and email addresses associated with any accounts where you've deﬁned permission sets appear. 2. Choose the account name (for example, Sandbox) where you applied the permission set (see Step 2.3). This will expand the list of permission sets that Nikki can choose from to manage her account. 3. Next to RegionalAdmin choose Management console to assume the role you deﬁned in the RegionalAdmin permission set. This will redirect you to the AWS Management Console home page. 4. In the upper-right corner of the console, choose your account name, and then choose Account. This will take you to the Account page. Notice that all other sections on this page display a message that you don't have the necessary permissions to view or modify those settings. 5. On the Account page, scroll down to the section AWS Regions. Select a checkbox for any available Region in the table. Notice that Nikki does have the necessary permissions to Enable or Disable the list of Regions for her account as was intended. Nicely done! Steps 1 through 3 helped you to successfully implement and test your SAML connection. Now, to complete the tutorial, we encourage you to move on to Step 4 to implement automatic provisioning. Step 4: Conﬁgure and test your SCIM synchronization In this step, you will set up automatic provisioning (synchronization) of user information from Microsoft Entra ID into IAM Identity Center using the SCIM v2.0 protocol. You conﬁgure this connection in Microsoft Entra ID using your SCIM endpoint for IAM Identity Center and a bearer token that is created automatically by IAM Identity Center. Step 4: Conﬁgure and test your SCIM synchronization 65 AWS IAM Identity Center User Guide When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in Microsoft Entra ID to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and Microsoft Entra ID. The following steps walk you through how to enable automatic provisioning of users that primarily reside in Microsoft Entra ID to IAM Identity Center using the IAM Identity Center app in Microsoft Entra ID. Step 4.1 > Step 4.1: Create a second test user in Microsoft Entra ID For testing purposes, you will create a new user (Richard Roe) in Microsoft Entra ID. Later, after you set up SCIM synchronization, you will test that this user and all relevant attributes were synced successfully to IAM Identity Center. 1. 2. 3. 4. 5. In the Microsoft Entra admin center console, navigate to Identity > Users > All users. Select New user, and then choose Create new user at the top of the screen. In User principal name, enter RichRoe, and then select your preferred domain and extension. For example, [email protected]. In Display name, enter RichRoe. In Password, enter a strong password or select the eye icon to show the password that was auto-generated, and either copy or write down the value that's displayed. 6. Choose Properties, and then provide the following values: • First name - Enter Richard • Last name - Enter Roe • Job title - Enter Marketing Lead • Department - Enter Sales • Employee ID - Enter 12345 7. Choose Review + create, and then choose Create. Step 4.2 > Step 4.2: Enable automatic provisioning in IAM Identity Center Step 4: Conﬁgure and test your SCIM synchronization 66 AWS IAM Identity Center User Guide In this procedure, you will use the IAM Identity Center console to enable automatic provisioning of users and groups coming from Microsoft Entra ID into IAM Identity Center. 1. Open the IAM Identity Center console, and choose Settings in the left navigation pane. 2. On the Settings page, under the Identity source tab, notice that Provisioning method is set to Manual. 3. 4. Locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. In the Inbound automatic provisioning dialog box, copy each of the values for the following options. You will need to paste these in the next step when you conﬁgure provisioning in Microsoft Entra ID. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Warning
sso-ug-031	sso-ug.pdf	31	Settings page, under the Identity source tab, notice that Provisioning method is set to Manual. 3. 4. Locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. In the Inbound automatic provisioning dialog box, copy each of the values for the following options. You will need to paste these in the next step when you conﬁgure provisioning in Microsoft Entra ID. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. 5. Choose Close. 6. Under the Identity source tab, notice that Provisioning method is now set to SCIM. Step 4.3 > Step 4.3: Conﬁgure automatic provisioning in Microsoft Entra ID Now that you have your RichRoe test user in place and have enabled SCIM in IAM Identity Center, you can proceed with conﬁguring the SCIM synchronization settings in Microsoft Entra ID. 1. In the Microsoft Entra admin center console, navigate to Identity > Applications > Enterprise applications and then choose AWS IAM Identity Center. 2. Choose Provisioning, under Manage, choose Provisioning again. Step 4: Conﬁgure and test your SCIM synchronization 67 AWS IAM Identity Center User Guide 3. In Provisioning Mode select Automatic. 4. Under Admin Credentials, in Tenant URL paste in the SCIM endpoint URL value you copied earlier in Step 4.2. In Secret Token, paste in the Access token value. 5. Choose Test Connection. You should see a message indicating that the tested credentials were successfully authorized to enable provisioning. 6. Choose Save. 7. Under Manage, choose Users and groups, and then choose Add user/group. 8. On the Add Assignment page, under Users, choose None Selected. 9. Select RichRoe, and then choose Select. 10. On the Add Assignment page, choose Assign. 11. Choose Overview, and then choose Start provisioning. Step 4.4 Step 4.4: Verify that synchronization occurred In this section, you will verify that Richard's user was successfully provisioned and that all attributes are displayed in IAM Identity Center. 1. In the IAM Identity Center console, choose Users. 2. On the Users page, you should see your RichRoe user displayed. Notice that in the Created by column the value is set to SCIM. 3. Choose RichRoe, under Proﬁle, verify that the following attributes were copied from Microsoft Entra ID. • First name - Richard • Last name - Roe • Department - Sales • Title - Marketing Lead • Employee number - 12345 Now that Richard's user has been created in IAM Identity Center, you can assign it to any permission set so you can control the level of access he has to your AWS resources. For example, you could assign RichRoe to the RegionalAdmin permission set you used earlier Step 4: Conﬁgure and test your SCIM synchronization 68 AWS IAM Identity Center User Guide to grant Nikki the permissions to manage Regions (see Step 2.3) and then test his level of access using Step 3.5. Congratulations! You have successfully set up a SAML connection between Microsoft and AWS and have veriﬁed that automatic provisioning is working to keep everything in sync. Now you can apply what you've learned to more smoothly set up your production environment. Step 5: Conﬁgure ABAC - Optional Now that you have successfully conﬁgured SAML and SCIM, you can optionally choose to conﬁgure attribute-based access control (ABAC). ABAC is an authorization strategy that deﬁnes permissions based on attributes. With Microsoft Entra ID, you can use either of the following two methods to conﬁgure ABAC for use with IAM Identity Center. Conﬁgure user attributes in Microsoft Entra ID for access control in IAM Identity Center Conﬁgure user attributes in Microsoft Entra ID for access control in IAM Identity Center In the following procedure, you will determine which attributes in Microsoft Entra ID should be used by IAM Identity Center to manage access to your AWS resources. Once deﬁned, Microsoft Entra ID sends these attributes to IAM Identity Center through SAML assertions. You will then need to Create a permission set in IAM Identity Center to manage access based on the attributes you passed from Microsoft Entra ID. Before you begin this procedure, you ﬁrst need to enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. 1. In the Microsoft Entra admin center console, navigate to Identity > Applications > Enterprise applications and then choose AWS IAM Identity Center. 2. Choose Single sign-on. 3. In the Attributes & Claims section, choose Edit. 4. On the Attributes & Claims page, do the following: Step 5: Conﬁgure ABAC - Optional
sso-ug-032	sso-ug.pdf	32	IAM Identity Center to manage access based on the attributes you passed from Microsoft Entra ID. Before you begin this procedure, you ﬁrst need to enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. 1. In the Microsoft Entra admin center console, navigate to Identity > Applications > Enterprise applications and then choose AWS IAM Identity Center. 2. Choose Single sign-on. 3. In the Attributes & Claims section, choose Edit. 4. On the Attributes & Claims page, do the following: Step 5: Conﬁgure ABAC - Optional 69 AWS IAM Identity Center User Guide a. b. c. d. e. Choose Add new claim For Name, enter AccessControl:AttributeName. Replace AttributeName with the name of the attribute you are expecting in IAM Identity Center. For example, AccessControl:Department. For Namespace, enter https://aws.amazon.com/SAML/Attributes. For Source, choose Attribute. For Source attribute, use the drop-down list to choose the Microsoft Entra ID user attributes. For example, user.department. 5. Repeat the previous step for each attribute you need to send to IAM Identity Center in the SAML assertion. 6. Choose Save. Conﬁgure ABAC using IAM Identity Center Conﬁgure ABAC using IAM Identity Center With this method, you use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/ SAML/Attributes/AccessControl:{TagKey}. You can use this element to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair Department=billing, use the following attribute: <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/ AccessControl:Department"> <saml:AttributeValue>billing </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. Step 5: Conﬁgure ABAC - Optional 70 AWS IAM Identity Center User Guide Assign access to AWS accounts The following steps are only required to grant access to AWS accounts only. These steps are not required to grant access to AWS applications. Note To complete this step, you'll need an Organization instance of IAM Identity Center. For more information, see Organization and account instances of IAM Identity Center. Step 1: IAM Identity Center: Grant Microsoft Entra ID users access to accounts 1. Return to the IAM Identity Center console. In the IAM Identity Center navigation pane, under Multi-account permissions, choose AWS accounts. 2. On the AWS accounts page the Organizational structure displays your organizational root with your accounts underneath it in the hierarchy. Select the checkbox for your management account, then select Assign users or groups. 3. The Assign users and groups workﬂow displays. It consists of three steps: a. b. For Step 1: Select users and groups choose the user that will be performing the administrator job function. Then choose Next. For Step 2: Select permission sets choose Create permission set to open a new tab that steps you through the three sub-steps involved in creating a permission set. i. For Step 1: Select permission set type complete the following: • In Permission set type, choose Predeﬁned permission set. • In Policy for predeﬁned permission set, choose AdministratorAccess. Choose Next. ii. For Step 2: Specify permission set details, keep the default settings, and choose Next. The default settings create a permission set named AdministratorAccess with session duration set to one hour. Assign access to AWS accounts 71 AWS IAM Identity Center User Guide iii. For Step 3: Review and create, verify that the Permission set type uses the AWS managed policy AdministratorAccess. Choose Create. On the Permission sets page a notiﬁcation appears informing you that the permission set was created. You can close this tab in your web browser now. iv. On the Assign users and groups browser tab, you are still on Step 2: Select permission sets from which you started the create permission set workﬂow. v. In the Permissions sets area, choose the Refresh button. The AdministratorAccess permission set you created appears in the list. Select the checkbox for that permission set and then choose Next. c. For Step 3: Review and submit review the selected user and permission set, then choose Submit. The page updates with a message that your AWS account is being conﬁgured. Wait until the process completes. You are returned to the AWS accounts page. A notiﬁcation message informs you that your AWS account has been reprovisioned and the updated permission set applied. When the user sign in they will have the option of choosing the AdministratorAccess role. Step 2: Microsoft Entra ID: Conﬁrm Microsoft Entra ID users access to AWS resources 1. Return to the Microsoft Entra ID console and navigate to your IAM Identity Center SAML- based Sign-on
sso-ug-033	sso-ug.pdf	33	the selected user and permission set, then choose Submit. The page updates with a message that your AWS account is being conﬁgured. Wait until the process completes. You are returned to the AWS accounts page. A notiﬁcation message informs you that your AWS account has been reprovisioned and the updated permission set applied. When the user sign in they will have the option of choosing the AdministratorAccess role. Step 2: Microsoft Entra ID: Conﬁrm Microsoft Entra ID users access to AWS resources 1. Return to the Microsoft Entra ID console and navigate to your IAM Identity Center SAML- based Sign-on application. 2. Select Users and groups and select Add users or groups. You’ll add the user you created in this tutorial in Step 4 to the Microsoft Entra ID application. By adding the user, you’ll allow them to sign-in to AWS. Search for the user you created at Step 4. If you followed this step, it would be RichardRoe. • For a demo, see Federate your existing IAM Identity Center instance with Microsoft Entra ID Troubleshooting For general SCIM and SAML troubleshooting with Microsoft Entra ID, see the following sections: Troubleshooting 72 AWS IAM Identity Center User Guide • Synchronization issues with Microsoft Entra ID and IAM Identity Center • Speciﬁc users fail to synchronize into IAM Identity Center from an external SCIM provider • Issues regarding contents of SAML assertions created by IAM Identity Center • Duplicate user or group error when provisioning users or groups with an external identity provider • Additional resources Synchronization issues with Microsoft Entra ID and IAM Identity Center If you are experiencing issues with Microsoft Entra ID users not synchronizing to IAM Identity Center, it might be due to a syntax issue that IAM Identity Center has ﬂagged when a new user is being added to IAM Identity Center. You can conﬁrm this by checking the Microsoft Entra ID audit logs for failed events, such as an 'Export'. The Status Reason for this event will state: {"schema":["urn:ietf:params:scim:api:messages:2.0:Error"],"detail":"Request is unparsable, syntactically incorrect, or violates schema.","status":"400"} You can also check AWS CloudTrail for the failed event. This can be done by searching in the Event History console of CloudTrail using the following ﬁlter: "eventName":"CreateUser" The error in the CloudTrail event will state the following: "errorCode": "ValidationException", "errorMessage": "Currently list attributes only allow single item“ Ultimately, this exception means that one of the values passed from Microsoft Entra ID contained more values than anticipated. The solution is to review the attributes of the user in Microsoft Entra ID, ensuring that none contain duplicate values. One common example of duplicate values is having multiple values present for contact numbers such as mobile, work, and fax. Although separate values, they are all passed to IAM Identity Center under the single parent attribute phoneNumbers. For general SCIM troubleshooting tips, see Troubleshooting. Troubleshooting 73 AWS IAM Identity Center User Guide Microsoft Entra ID Guest Account Synchronization If you would like to sync your Microsoft Entra ID guest users to IAM Identity Center, see the following procedure. Microsoft Entra ID guest users’ email is diﬀerent than Microsoft Entra ID users. This diﬀerence causes issues when attempting to synchronize Microsoft Entra ID guest users with IAM Identity Center. For example, see the following email address for a guest user: exampleuser_domain.com#[email protected]. IAM Identity Center expects the email address of a user to not contain the EXT@domain format. 1. Sign in to the Microsoft Entra admin center and navigate to Identity > Applications > Enterprise applications and then choose AWS IAM Identity Center 2. Navigate to the Single Sign On tab in the left pane. 3. 4. Select Edit which appears next to User Attributes & Claims. Select Unique User Identiﬁer (Name ID) following Required Claims. 5. You will create two claim conditions for your Microsoft Entra ID users and guest users: a. For Microsoft Entra ID users, create a user type for members with source attribute set to user.userprincipalname. b. For Microsoft Entra ID guest users, create a user type for external guests with the source attribute set to user.mail. c. Select Save and retry signing in as a Microsoft Entra ID guest user. Additional resources • For general SCIM troubleshooting tips, see Troubleshooting IAM Identity Center issues. • For Microsoft Entra ID troubleshooting, see Microsoft documentation. • To learn more about federation across multiple AWS accounts, see Securing AWS accounts with Azure Active Directory Federation. The following resources can help you troubleshoot as you work with AWS: • AWS re:Post - Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support Troubleshooting 74 AWS IAM Identity Center User Guide Conﬁgure SAML and SCIM with Okta and IAM Identity Center You can automatically provision or synchronize user and group information from Okta into IAM
sso-ug-034	sso-ug.pdf	34	Troubleshooting IAM Identity Center issues. • For Microsoft Entra ID troubleshooting, see Microsoft documentation. • To learn more about federation across multiple AWS accounts, see Securing AWS accounts with Azure Active Directory Federation. The following resources can help you troubleshoot as you work with AWS: • AWS re:Post - Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support Troubleshooting 74 AWS IAM Identity Center User Guide Conﬁgure SAML and SCIM with Okta and IAM Identity Center You can automatically provision or synchronize user and group information from Okta into IAM Identity Center using the System for Cross-domain Identity Management (SCIM) 2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. To conﬁgure this connection in Okta, you use your SCIM endpoint for IAM Identity Center and a bearer token that is created automatically by IAM Identity Center. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in Okta to the named attributes in IAM Identity Center. This mapping matches the expected user attributes between IAM Identity Center and your Okta account. Okta supports the following provisioning features when connected to IAM Identity Center through SCIM: • Create users – Users assigned to the IAM Identity Center application in Okta are provisioned in IAM Identity Center. • Update user attributes – Attribute changes for users who are assigned to the IAM Identity Center application in Okta are updated in IAM Identity Center. • Deactivate users – Users who are unassigned from the IAM Identity Center application in Okta are disabled in IAM Identity Center. • Group push – Groups (and their members) in Okta are synchronized to IAM Identity Center. Note To minimize administrative overhead in both Okta and IAM Identity Center, we recommend that you assign and push groups instead of individual users. Objective In this tutorial, you will walk through setting up a SAML connection with Okta IAM Identity Center. Later, you will synchronize users from Okta, using SCIM. In this scenario, you manage all users and groups in Okta. Users sign in through the Okta portal. To verify everything is conﬁgured correctly, after completing the conﬁguration steps you will sign in as an Okta user and verify access to AWS resources. Okta 75 AWS IAM Identity Center Note User Guide You can sign up for an Okta account (free trial) that has Okta's IAM Identity Center application installed. For paid Okta products, you might need to conﬁrm that your Okta license supports lifecycle management or similar capabilities that enable outbound provisioning. These features might be necessary to conﬁgure SCIM from Okta to IAM Identity Center. If you haven't enabled IAM Identity Center yet, see Enable IAM Identity Center. Considerations • Before you conﬁgure SCIM provisioning between Okta and IAM Identity Center, we recommend that you ﬁrst review Considerations for using automatic provisioning. • Every Okta user must have a First name, Last name, Username and Display name value speciﬁed. • Each Okta user has only a single value per data attribute, such as email address or phone number. Any users that have multiple values will fail to synchronize. If there are users that have multiple values in their attributes, remove the duplicate attributes before attempting to provision the user in IAM Identity Center. For example, only one phone number attribute can be synchronized, since the default phone number attribute is "work phone", use the "work phone" attribute to store the user's phone number, even if the phone number for the user is a home phone or a mobile phone. • When using Okta with IAM Identity Center, IAM Identity Center is generally conﬁgured as an Application in Okta. This allows you to conﬁgure multiple instances of IAM Identity Center as multiple applications, supporting access to multiple AWS Organizations, within a single instance of the Okta. • Entitlements and role attributes aren't supported and can't be synchronized with IAM Identity Center. • Using the same Okta group for both assignments and group push isn't currently supported. To maintain consistent group memberships between Okta and IAM Identity Center, create a separate group and conﬁgure it to push groups to IAM Identity Center. Considerations 76 AWS IAM Identity Center User Guide Step 1: Okta: Obtain the SAML metadata from your Okta account 1. Sign in to the Okta admin dashboard, expand Applications, then select Applications. 2. On the Applications page, choose Browse App Catalog. 3. In the search box, type AWS IAM Identity Center, select the app to add the IAM Identity Center app. 4. Select the Sign On tab. 5. Under SAML Signing Certiﬁcates, select Actions, and then select View IdP Metadata. A new browser tab opens showing the document tree of an XML ﬁle. Select all of the XML
sso-ug-035	sso-ug.pdf	35	Identity Center. Considerations 76 AWS IAM Identity Center User Guide Step 1: Okta: Obtain the SAML metadata from your Okta account 1. Sign in to the Okta admin dashboard, expand Applications, then select Applications. 2. On the Applications page, choose Browse App Catalog. 3. In the search box, type AWS IAM Identity Center, select the app to add the IAM Identity Center app. 4. Select the Sign On tab. 5. Under SAML Signing Certiﬁcates, select Actions, and then select View IdP Metadata. A new browser tab opens showing the document tree of an XML ﬁle. Select all of the XML from <md:EntityDescriptor> to </md:EntityDescriptor> and copy it to a text ﬁle. 6. Save the text ﬁle as metadata.xml. Leave the Okta admin dashboard open, you will continue using this console in the later steps. Step 2: IAM Identity Center: Conﬁgure Okta as the identity source for IAM Identity Center 1. Open the IAM Identity Center console as a user with administrative privileges. 2. Choose Settings in the left navigation pane. 3. On the Settings page, choose Actions, and then choose Change identity source. 4. Under Choose identity source, select External identity provider, and then choose Next. 5. Under Conﬁgure external identity provider, do the following: a. Under Service provider metadata, choose Download metadata ﬁle to download the IAM Identity Center metadata ﬁle and save it on your system. You will provide the IAM Identity Center SAML metadata ﬁle to Okta later in this tutorial. Copy the following items to a text ﬁle for easy access: • IAM Identity Center Assertion Consumer Service (ACS) URL • IAM Identity Center issuer URL You'll need these values later in this tutorial. b. Under Identity provider metadata, under IdP SAML metadata, select Choose ﬁle and then select the metadata.xml ﬁle you created in the previous step. Step 1: Okta: Obtain the SAML metadata from your Okta account 77 AWS IAM Identity Center c. Choose Next. User Guide 6. After you read the disclaimer and are ready to proceed, enter ACCEPT. 7. Choose Change identity source. Leave the AWS console open, you will continue using this console in the next step. 8. Return to the Okta admin dashboard and select the Sign On tab of the AWS IAM Identity Center app, then select Edit. 9. Under Advanced Sign-on Settings enter the following: • For ACS URL, enter the value you copied for IAM Identity Center Assertion Consumer Service (ACS) URL • For Issuer URL, enter the value you copied for IAM Identity Center issuer URL • For Application username format, select one of the options from the menu. Ensure the value you choose is unique for each user. For this tutorial, select Okta username 10. Choose Save. You are now ready to provision users from Okta to IAM Identity Center. Leave the Okta admin dashboard open, and return to the IAM Identity Center console for the next step. Step 3: IAM Identity Center and Okta: Provision Okta users 1. 2. In the IAM Identity Center console on the Settings page, locate the Automatic provisioning information box, and then choose Enable. This enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. In the Inbound automatic provisioning dialog box, copy each of the values for the following options: a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Step 3: IAM Identity Center and Okta: Provision Okta users 78 AWS IAM Identity Center User Guide Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in Okta later in this tutorial. 3. Choose Close. 4. Return to the Okta admin dashboard and navigate to the IAM Identity Center app. 5. On the IAM Identity Center app page, choose the Provisioning tab, and then in the left navigation under Settings, choose Integration. 6. Choose Edit, and then select the checkbox next to Enable API integration to enable automatic provisioning. 7. Conﬁgure Okta with the SCIM provisioning values from AWS IAM Identity Center that you copied earlier in this step: a. b. In the Base URL ﬁeld, enter the SCIM endpoint value. In the API Token ﬁeld, enter the Access token value. 8. Choose Test API Credentials to verify the credentials entered are valid. The message AWS IAM Identity Center was veriﬁed successfully! displays. 9. Choose Save. You're moved to the Settings section, with Integration selected. 10. Under Settings, choose To App, and then select the Enable checkbox for each of the Provisioning to App features you want to enable. For this tutorial, select all the options. 11. Choose Save. You are now ready to synchronize your users from
sso-ug-036	sso-ug.pdf	36	step: a. b. In the Base URL ﬁeld, enter the SCIM endpoint value. In the API Token ﬁeld, enter the Access token value. 8. Choose Test API Credentials to verify the credentials entered are valid. The message AWS IAM Identity Center was veriﬁed successfully! displays. 9. Choose Save. You're moved to the Settings section, with Integration selected. 10. Under Settings, choose To App, and then select the Enable checkbox for each of the Provisioning to App features you want to enable. For this tutorial, select all the options. 11. Choose Save. You are now ready to synchronize your users from Okta with IAM Identity Center. Step 4: Okta: Synchronize users from Okta with IAM Identity Center By default, no groups or users are assigned to your Okta IAM Identity Center app. Provisioning groups provisions the users that are members of the group. Complete the following steps to synchronize groups and users with AWS IAM Identity Center. 1. In the Okta IAM Identity Center app page, choose the Assignments tab. You can assign both people and groups to the IAM Identity Center app. Step 4: Okta: Synchronize users from Okta with IAM Identity Center 79 AWS IAM Identity Center a. To assign people: User Guide • In the Assignments page, choose Assign, and then choose Assign to people. • Choose the Okta users that you want to have access to the IAM Identity Center app. Choose Assign, choose Save and Go Back, and then choose Done. This starts the process of provisioning the users into IAM Identity Center. b. To assign groups: • In the Assignments page, choose Assign, and then choose Assign to groups. • Choose the Okta groups that you want to have access to the IAM Identity Center app. Choose Assign, choose Save and Go Back, and then choose Done. This starts the process of provisioning the users in the group into IAM Identity Center. Note You might be required to specify additional attributes for the group if they aren't present in all of the user records. The attributes speciﬁed for the group will override any individual attribute values. 2. Choose the Push Groups tab. Choose the Okta group you want to synchronize with IAM Identity Center. Choose Save. The group status changes to Active after the group and its members have been pushed to IAM Identity Center. 3. Return to the Assignments tab. 4. To add individual Okta users to IAM Identity Center, use the following steps: a. In the Assignments page, choose Assign, and then choose Assign to People. b. Choose the Okta users that you want to have access to the IAM Identity Center app. Choose Assign, choose Save and Go Back, and then choose Done. This starts the process of provisioning the individual users into IAM Identity Center. Step 4: Okta: Synchronize users from Okta with IAM Identity Center 80 AWS IAM Identity Center User Guide Note You can also assign users and groups to the AWS IAM Identity Center app, from the Applications page of the Okta admin dashboard. To do this select the Settings icon and then choose Assign to Users or Assign to Groups and then specify the user or group. 5. Return to the IAM Identity Center console. In the left navigation, select Users, you should see the user list populated by your Okta users. Congratulations! You have successfully set up a SAML connection between Okta and AWS and have veriﬁed that automatic provisioning is working. You can now assign these users to accounts and applications in IAM Identity Center. For this tutorial, in the next step let's designate one of the users as the IAM Identity Center administrator by granting them administrative permissions to the management account. Passing attributes for access control - Optional You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> Passing attributes for access control - Optional 81 AWS IAM Identity Center User Guide If you need to add multiple attributes, include a separate Attribute element for each tag. Assign access to AWS accounts The following steps are only required to grant access to AWS accounts only. These steps are not required to grant access to AWS applications. Note To complete this step, you'll need an Organization instance of IAM Identity Center. For more information, see Organization
sso-ug-037	sso-ug.pdf	37	tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> Passing attributes for access control - Optional 81 AWS IAM Identity Center User Guide If you need to add multiple attributes, include a separate Attribute element for each tag. Assign access to AWS accounts The following steps are only required to grant access to AWS accounts only. These steps are not required to grant access to AWS applications. Note To complete this step, you'll need an Organization instance of IAM Identity Center. For more information, see Organization and account instances of IAM Identity Center. Step 1: IAM Identity Center: Grant Okta users access to accounts 1. In the IAM Identity Center navigation pane, under Multi-account permissions, choose AWS accounts. 2. On the AWS accounts page the Organizational structure displays your organizational root with your accounts underneath it in the hierarchy. Select the checkbox for your management account, then select Assign users or groups. 3. The Assign users and groups workﬂow displays. It consists of three steps: a. b. For Step 1: Select users and groups, choose the user that will be performing the administrator job function. Then choose Next. For Step 2: Select permission sets, choose Create permission set to open a new tab that walks you through the three sub-steps involved in creating a permission set. i. For Step 1: Select permission set type complete the following: • In Permission set type, choose Predeﬁned permission set. • In Policy for predeﬁned permission set, choose AdministratorAccess. Choose Next. ii. For Step 2: Specify permission set details, keep the default settings, and choose Next. The default settings create a permission set named AdministratorAccess with session duration set to one hour. Assign access to AWS accounts 82 AWS IAM Identity Center User Guide iii. For Step 3: Review and create, verify that the Permission set type uses the AWS managed policy AdministratorAccess. Choose Create. On the Permission sets page, a notiﬁcation appears informing you that the permission set was created. You can close this tab in your web browser now. On the Assign users and groups browser tab, you are still on Step 2: Select permission sets from which you started the create permission set workﬂow. In the Permissions sets area, choose the Refresh button. The AdministratorAccess permission set you created appears in the list. Select the checkbox for that permission set and then choose Next. c. For Step 3: Review and submit, review the selected user and permission set, then choose Submit. The page updates with a message that your AWS account is being conﬁgured. Wait until the process completes. You are returned to the AWS accounts page. A notiﬁcation message informs you that your AWS account has been reprovisioned and the updated permission set applied. When the user signs-in they will have the option of choosing the AdministratorAccess role. Step 2: Okta: Conﬁrm Okta users access to AWS resources 1. Sign in using a test account to the Okta dashboard. 2. Under My Apps, select the AWS IAM Identity Center icon. 3. You should see the AWS account icon. Expand that icon to see the list of AWS accounts that the user can access. In this tutorial you only worked with a single account, so expanding the icon only shows one account. 4. Select the account to display the permission sets available to the user. In this tutorial you created the AdministratorAccess permission set. 5. Next to the permission set are links for the type of access available for that permission set. When you created the permission set, you speciﬁed access to both the AWS Management Console and programmatic access. Select Management console to open the AWS Management Console. 6. The user is signed in to the AWS Management Console. Assign access to AWS accounts 83 AWS IAM Identity Center Next steps User Guide Now that you've conﬁgured Okta as an identity provider and provisioned users in IAM Identity Center, you can: • Grant access to AWS accounts, see Assign user or group access to AWS accounts. • Grant access to cloud applications, see Assign user access to applications in the IAM Identity Center console. • Conﬁgure permissions based on job functions, see Create a permission set. Troubleshooting For general SCIM and SAML troubleshooting with Okta, see the following sections: • Reprovisioning users and groups deleted from IAM Identity Center • Automatic Provisioning Error in Okta • Speciﬁc users fail to synchronize into IAM Identity Center from an external SCIM provider • Issues regarding contents of SAML assertions created by IAM Identity Center • Duplicate user or group error when provisioning users or groups with an external identity provider • Additional resources Reprovisioning users and groups deleted from IAM Identity Center • You could receive the following
sso-ug-038	sso-ug.pdf	38	permissions based on job functions, see Create a permission set. Troubleshooting For general SCIM and SAML troubleshooting with Okta, see the following sections: • Reprovisioning users and groups deleted from IAM Identity Center • Automatic Provisioning Error in Okta • Speciﬁc users fail to synchronize into IAM Identity Center from an external SCIM provider • Issues regarding contents of SAML assertions created by IAM Identity Center • Duplicate user or group error when provisioning users or groups with an external identity provider • Additional resources Reprovisioning users and groups deleted from IAM Identity Center • You could receive the following error message in the Okta Console, if you're attempting to change either a user or group in Okta that was once synchronized and then deleted from IAM Identity Center: • Automatic proﬁle push of user Jane Doe to app AWS IAM Identity Center failed: Error while trying to push proﬁle update for [email protected]: No user returned for user xxxxx- xxxxxx-xxxxx-xxxxxxx • Linked group is missing in AWS IAM Identity Center. Change the linked group to resume pushing group memberships. • You could also receive the following error message in the Okta's Systems Logs for either synchronized and deleted IAM Identity Center users or groups: Next steps 84 AWS IAM Identity Center User Guide • Okta Error: Eventfailed application.provision.user.push_proﬁle : No user returned for user xxxxx-xxxxxx-xxxxx-xxxxxxx • Okta Error: application.provision.group_push.mapping.update.or.delete.failed.with.error : Linked group is missing in AWS IAM Identity Center. Change the linked group to resume pushing group memberships. Warning Users and groups should be deleted from Okta rather than IAM Identity Center if you have synchronized Okta and IAM Identity Center using SCIM. Troubleshooting deleted IAM Identity Center Users To address this issue with deleted IAM Identity Center users, the users must be deleted from Okta. If necessary, these users would also need to be recreated in Okta. When the user is recreated in Okta, it will also be reprovisioned into the IAM Identity Center through SCIM. For more information on deleting a user, see Okta documentation. Note If you need to remove a Okta user’s access to IAM Identity Center, you should ﬁrst remove them from their Group Push and then their Assignment Group in Okta. This ensures the user is removed from their associated group membership in IAM Identity Center. For more information on troubleshooting Group Push, see Okta documentation. Troubleshooting deleted IAM Identity Center Groups To address this issue with deleted IAM Identity Center groups, the group must be deleted from Okta. If necessary, these groups would also need to be recreated in Okta using Group Push. When the user is recreated in Okta, it will also be reprovisioned into the IAM Identity Center through SCIM. For more information on deleting a group, see Okta documentation. Automatic Provisioning Error in Okta If you receive the following error message in Okta: Troubleshooting 85 AWS IAM Identity Center User Guide Automatic provisioning of user Jane Doe to app AWS IAM Identity Center failed: Matching user not found See Okta documentation for more information. Additional resources • For general SCIM troubleshooting tips, see Troubleshooting IAM Identity Center issues. The following resources can help you troubleshoot as you work with AWS: • AWS re:Post - Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support Setting up SCIM provisioning between OneLogin and IAM Identity Center IAM Identity Center supports automatic provisioning (synchronization) of user and group information from OneLogin into IAM Identity Center using the System for Cross-domain Identity Management (SCIM) v2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. You conﬁgure this connection in OneLogin, using your SCIM endpoint for IAM Identity Center and a bearer token that is created automatically by IAM Identity Center. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in OneLogin to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and OneLogin. The following steps walk you through how to enable automatic provisioning of users and groups from OneLogin to IAM Identity Center using the SCIM protocol. Note Before you begin deploying SCIM, we recommend that you ﬁrst review the Considerations for using automatic provisioning. Topics OneLogin 86 AWS IAM Identity Center • Prerequisites • Step 1: Enable provisioning in IAM Identity Center • Step 2: Conﬁgure provisioning in OneLogin User Guide • (Optional) Step 3: Conﬁgure user attributes in OneLogin for access control in IAM Identity Center • (Optional) Passing attributes for access control • Troubleshooting Prerequisites You will need the following before you can get started: • A OneLogin account. If you do not have an existing account, you may be able to obtain a free trial or developer account from the OneLogin
sso-ug-039	sso-ug.pdf	39	that you ﬁrst review the Considerations for using automatic provisioning. Topics OneLogin 86 AWS IAM Identity Center • Prerequisites • Step 1: Enable provisioning in IAM Identity Center • Step 2: Conﬁgure provisioning in OneLogin User Guide • (Optional) Step 3: Conﬁgure user attributes in OneLogin for access control in IAM Identity Center • (Optional) Passing attributes for access control • Troubleshooting Prerequisites You will need the following before you can get started: • A OneLogin account. If you do not have an existing account, you may be able to obtain a free trial or developer account from the OneLogin website. • An IAM Identity Center-enabled account (free). For more information, see Enable IAM Identity Center. • A SAML connection from your OneLogin account to IAM Identity Center. For more information, see Enabling Single Sign-On Between OneLogin and AWS on the AWS Partner Network Blog. Step 1: Enable provisioning in IAM Identity Center In this ﬁrst step, you use the IAM Identity Center console to enable automatic provisioning. To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Prerequisites 87 AWS IAM Identity Center User Guide Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in your IdP later in this tutorial. 5. Choose Close. You have now set up provisioning in the IAM Identity Center console. Now you need to do the remaining tasks using the OneLogin admin console as described in the following procedure. Step 2: Conﬁgure provisioning in OneLogin Use the following procedure in the OneLogin admin console to enable integration between IAM Identity Center and the IAM Identity Center app. This procedure assumes you have already conﬁgured the AWS Single Sign-On application in OneLogin for SAML authentication. If you have not yet created this SAML connection, please do so before proceeding and then return here to complete the SCIM provisioning process. For more information about conﬁguring SAML with OneLogin, see Enabling Single Sign-On Between OneLogin and AWS on the AWS Partner Network Blog. To conﬁgure provisioning in OneLogin 1. Sign in to OneLogin, and then navigate to Applications > Applications. 2. On the Applications page, search for the application you created previously to form your SAML connection with IAM Identity Center. Choose it and then choose Conﬁguration from the navigation pane. 3. In the previous procedure, you copied the SCIM endpoint value in IAM Identity Center. Paste that value into the SCIM Base URL ﬁeld in OneLogin. Also, in the previous procedure you copied the Access token value in IAM Identity Center. Paste that value into the SCIM Bearer Token ﬁeld in OneLogin. 4. Next to API Connection, click Enable, and then click Save to complete the conﬁguration. 5. 6. In the navigation pane, choose Provisioning. Select the check boxes for Enable provisioning, Create user, Delete user, and Update user, and then choose Save. Step 2: Conﬁgure provisioning in OneLogin 88 AWS IAM Identity Center User Guide 7. In the navigation pane, choose Users. 8. Click More Actions and choose Sync logins. You should receive the message Synchronizing users with AWS Single Sign-On. 9. Click More Actions again, and then choose Reapply entitlement mappings. You should receive the message Mappings are being reapplied. 10. At this point, the provisioning process should begin. To conﬁrm this, navigate to Activity > Events, and monitor the progress. Successful provisioning events, as well as errors, should appear in the event stream. 11. To verify that your users and groups have all been successfully synchronized to IAM Identity Center, return to the IAM Identity Center console and choose Users. Your synchronized users from OneLogin appear on the Users page. You can also view your synchronized groups on the Groups page. 12. To synchronize user changes automatically to IAM Identity Center, navigate to the Provisioning page, locate the Require admin approval before this action is performed section, de-select Create User, Delete User, and/or Update User, and click Save. (Optional) Step 3: Conﬁgure user attributes in OneLogin for access control in IAM Identity Center This is an optional procedure for OneLogin if you choose to conﬁgure attributes you
sso-ug-040	sso-ug.pdf	40	IAM Identity Center, return to the IAM Identity Center console and choose Users. Your synchronized users from OneLogin appear on the Users page. You can also view your synchronized groups on the Groups page. 12. To synchronize user changes automatically to IAM Identity Center, navigate to the Provisioning page, locate the Require admin approval before this action is performed section, de-select Create User, Delete User, and/or Update User, and click Save. (Optional) Step 3: Conﬁgure user attributes in OneLogin for access control in IAM Identity Center This is an optional procedure for OneLogin if you choose to conﬁgure attributes you will use in IAM Identity Center to manage access to your AWS resources. The attributes that you deﬁne in OneLogin are passed in a SAML assertion to IAM Identity Center. You will then create a permission set in IAM Identity Center to manage access based on the attributes you passed from OneLogin. Before you begin this procedure, you must ﬁrst enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. To conﬁgure user attributes in OneLogin for access control in IAM Identity Center 1. Sign in to OneLogin, and then navigate to Applications > Applications. 2. On the Applications page, search for the application you created previously to form your SAML connection with IAM Identity Center. Choose it and then choose Parameters from the navigation pane. 3. In the Required Parameters section, do the following for each attribute you want to use in IAM Identity Center: (Optional) Step 3: Conﬁgure user attributes in OneLogin for access control in IAM Identity Center 89 AWS IAM Identity Center User Guide a. b. Choose +. In Field name, enter https://aws.amazon.com/SAML/Attributes/ AccessControl:AttributeName, and replace AttributeName with the name of the attribute you are expecting in IAM Identity Center. For example, https:// aws.amazon.com/SAML/Attributes/AccessControl:Department. c. Under Flags, check the box next to Include in SAML assertion, and choose Save. d. In the Value ﬁeld, use the drop-down list to choose the OneLogin user attributes. For example, Department. 4. Choose Save. (Optional) Passing attributes for access control You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. Troubleshooting The following can help you troubleshoot some common issues you might encounter while setting up automatic provisioning with OneLogin. Groups are not provisioned to IAM Identity Center (Optional) Passing attributes for access control 90 AWS IAM Identity Center User Guide By default, groups may not be provisioned from OneLogin to IAM Identity Center. Ensure that you’ve enabled group provisioning for your IAM Identity Center application in OneLogin. To do this, sign in to the OneLogin admin console, and check to make sure that the Include in User Provisioning option is selected under the properties of the IAM Identity Center application (IAM Identity Center application > Parameters > Groups). For more details on how to create groups in OneLogin, including how to synchronize OneLogin roles as groups in SCIM, please see the OneLogin website. Nothing is synchronized from OneLogin to IAM Identity Center, despite all settings being correct In addition to the note above regarding admin approval, you will need to Reapply entitlement mappings for many conﬁguration changes to take eﬀect. This can be found in Applications > Applications > IAM Identity Center application > More Actions. You can see details and logs for most actions in OneLogin, including synchronization events, under Activity > Events. I’ve deleted or disabled a group in OneLogin, but it still appears in IAM Identity Center OneLogin currently does not support the SCIM DELETE operation for groups, which means that the group continues to exist in IAM Identity Center. You must therefore remove the group from IAM Identity Center directly to ensure that any corresponding permissions in IAM Identity Center for that group are removed. I deleted a group in IAM Identity Center without ﬁrst deleting it from OneLogin and now I’m having user/group sync issues To remedy this situation, ﬁrst ensure that you do not have any redundant group provisioning rules or conﬁgurations in OneLogin. For example, a group directly assigned to an application along with a rule that publishes to the same group. Next, delete any undesirable
sso-ug-041	sso-ug.pdf	41	that the group continues to exist in IAM Identity Center. You must therefore remove the group from IAM Identity Center directly to ensure that any corresponding permissions in IAM Identity Center for that group are removed. I deleted a group in IAM Identity Center without ﬁrst deleting it from OneLogin and now I’m having user/group sync issues To remedy this situation, ﬁrst ensure that you do not have any redundant group provisioning rules or conﬁgurations in OneLogin. For example, a group directly assigned to an application along with a rule that publishes to the same group. Next, delete any undesirable groups in IAM Identity Center. Finally, in OneLogin, Refresh the entitlements (IAM Identity Center App > Provisioning > Entitlements), and then Reapply entitlement mappings (IAM Identity Center App > More Actions). To avoid this issue in the future, ﬁrst make the change to stop provisioning the group in OneLogin, then delete the group from IAM Identity Center. Using Ping Identity products with IAM Identity Center The following Ping Identity products have been tested with IAM Identity Center. Topics Ping Identity 91 AWS IAM Identity Center • PingFederate • PingOne PingFederate User Guide IAM Identity Center supports automatic provisioning (synchronization) of user and group information from the PingFederate product by Ping Identity (hereafter “Ping”) into IAM Identity Center. This provisioning uses the System for Cross-domain Identity Management (SCIM) v2.0 protocol. For more information, see Using SAML and SCIM identity federation with external identity providers. You conﬁgure this connection in PingFederate using your IAM Identity Center SCIM endpoint and access token. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in PingFederate to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and PingFederate. This guide is based on PingFederate version 10.2. Steps for other versions may vary. Contact Ping for more information about how to conﬁgure provisioning to IAM Identity Center for other versions of PingFederate. The following steps walk you through how to enable automatic provisioning of users and groups from PingFederate to IAM Identity Center using the SCIM protocol. Note Before you begin deploying SCIM, we recommend that you ﬁrst review the Considerations for using automatic provisioning. Then continue reviewing additional considerations in the next section. Topics • Prerequisites • Considerations • Step 1: Enable provisioning in IAM Identity Center • Step 2: Conﬁgure provisioning in PingFederate • (Optional) Step 3: Conﬁgure user attributes in PingFederate for access control in IAM Identity Center PingFederate 92 AWS IAM Identity Center User Guide • (Optional) Passing attributes for access control • Troubleshooting Prerequisites You'll need the following before you can get started: • A working PingFederate server. If you do not have an existing PingFederate server, you might be able to obtain a free trial or developer account from the Ping Identity website. The trial includes licenses and software downloads and associated documentation. • A copy of the PingFederate IAM Identity Center Connector software installed on your PingFederate server. For more information about how to obtain this software, see IAM Identity Center Connector on the Ping Identity website. • An IAM Identity Center-enabled account (free). For more information, see Enable IAM Identity Center. • A SAML connection from your PingFederate instance to IAM Identity Center. For instructions on how to conﬁgure this connection, see the PingFederate documentation. In summary, the recommended path is to use the IAM Identity Center Connector to conﬁgure "Browser SSO" in PingFederate, using the “download" and "import" metadata features on both ends to exchange SAML metadata between PingFederate and IAM Identity Center. Considerations The following are important considerations about PingFederate that can aﬀect how you implement provisioning with IAM Identity Center. • If an attribute (such as a phone number) is removed from a user in the data store conﬁgured in PingFederate, that attribute will not be removed from the corresponding user in IAM Identity Center. This is a known limitation in PingFederate’s provisioner implementation. If an attribute is changed to a diﬀerent (non-empty) value on a user, that change will be synchronized to IAM Identity Center. Step 1: Enable provisioning in IAM Identity Center In this ﬁrst step, you use the IAM Identity Center console to enable automatic provisioning. PingFederate 93 AWS IAM Identity Center User Guide To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when
sso-ug-042	sso-ug.pdf	42	Center console to enable automatic provisioning. PingFederate 93 AWS IAM Identity Center User Guide To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in your IdP later in this tutorial. 5. Choose Close. Now that you have set up provisioning in the IAM Identity Center console, you must complete the remaining tasks using the PingFederate administrative console., The steps are described in the following procedure. Step 2: Conﬁgure provisioning in PingFederate Use the following procedure in the PingFederate administrative console to enable integration between IAM Identity Center and the IAM Identity Center Connector. This procedure assumes that you have already installed the IAM Identity Center Connector software. If you have not yet done so, refer to Prerequisites, and then complete this procedure to conﬁgure SCIM provisioning. Important If your PingFederate server has not been previously conﬁgured for outbound SCIM provisioning, you may need to make a conﬁguration ﬁle change to enable provisioning. PingFederate 94 AWS IAM Identity Center User Guide For more information, see Ping documentation. In summary, you must modify the pf.provisioner.mode setting in the pingfederate-<version>/pingfederate/bin/ run.properties ﬁle to a value other than OFF (which is the default), and restart the server if currently running. For example, you may choose to use STANDALONE if you don’t currently have a high-availability conﬁguration with PingFederate. To conﬁgure provisioning in PingFederate 1. 2. 3. 4. 5. Sign on to the PingFederate administrative console. Select Applications from the top of the page, then click SP Connections. Locate the application you created previously to form your SAML connection with IAM Identity Center, and click on the connection name. Select Connection Type from the dark navigation headings near the top of the page. You should see Browser SSO already selected from your previous conﬁguration of SAML. If not, you must complete those steps ﬁrst before you can continue. Select the Outbound Provisioning check box, choose IAM Identity Center Cloud Connector as the type, and click Save. If IAM Identity Center Cloud Connector does not appear as an option, ensure that you have installed the IAM Identity Center Connector and have restarted your PingFederate server. 6. Click Next repeatedly until you arrive on the Outbound Provisioning page, and then click the Conﬁgure Provisioning button. 7. In the previous procedure, you copied the SCIM endpoint value in IAM Identity Center. Paste that value into the SCIM URL ﬁeld in the PingFederate console. Also, in the previous procedure you copied the Access token value in IAM Identity Center. Paste that value into the Access Token ﬁeld in the PingFederate console. Click Save. 8. On the Channel Conﬁguration (Conﬁgure Channels) page, click Create. 9. Enter a Channel Name for this new provisioning channel (such as AWSIAMIdentityCenterchannel), and click Next. 10. On the Source page, choose the Active Data Store you want to use for your connection to IAM Identity Center, and click Next. PingFederate 95 AWS IAM Identity Center Note User Guide If you have not yet conﬁgured a data source, you must do so now. See the Ping product documentation for information on how to choose and conﬁgure a data source in PingFederate. 11. On the Source Settings page, conﬁrm all values are correct for your installation, then click Next. 12. On the Source Location page, enter settings appropriate to your data source, and then click Next. For example, if using Active Directory as an LDAP directory: a. b. c. d. Enter the Base DN of your AD forest (such as DC=myforest,DC=mydomain,DC=com). In Users > Group DN, specify a single group that contains all of the users that you want to provision to IAM Identity Center. If no such single group exists, create that group in AD, return to this setting, and then enter the corresponding DN. Specify whether to search subgroups (Nested Search), and any required LDAP Filter. In Groups > Group DN, specify a single group that contains all of the groups that you want to provision to IAM Identity Center. In many cases, this may be the same DN as
sso-ug-043	sso-ug.pdf	43	Base DN of your AD forest (such as DC=myforest,DC=mydomain,DC=com). In Users > Group DN, specify a single group that contains all of the users that you want to provision to IAM Identity Center. If no such single group exists, create that group in AD, return to this setting, and then enter the corresponding DN. Specify whether to search subgroups (Nested Search), and any required LDAP Filter. In Groups > Group DN, specify a single group that contains all of the groups that you want to provision to IAM Identity Center. In many cases, this may be the same DN as you speciﬁed in the Users section. Enter Nested Search and Filter values as required. 13. On the Attribute Mapping page, ensure the following, and then click Next: a. The userName ﬁeld must be mapped to an Attribute that is formatted as an email ([email protected]). It must also match the value that the user will use to log in to Ping. This value in turn is populated in the SAML nameId claim during federated authentication and used for matching to the user in IAM Identity Center. For example, when using Active Directory, you may choose to specify the UserPrincipalName as the userName. b. Other ﬁelds suﬃxed with a * must be mapped to attributes that are non-null for your users. 14. On the Activation & Summary page, set the Channel Status to Active to cause the synchronization to start immediately after the conﬁguration is saved. 15. Conﬁrm that all conﬁguration values on the page are correct, and click Done. 16. On the Manage Channels page, click Save. 17. At this point, provisioning starts. To conﬁrm activity, you can view the provisioner.log ﬁle, located by default in the pingfederate-<version>/pingfederate/log directory on your PingFederate server. PingFederate 96 AWS IAM Identity Center User Guide 18. To verify that users and groups have been successfully synchronized to IAM Identity Center, return to the IAM Identity Center Console and choose Users. Synchronized users from PingFederate appear on the Users page. You can also view synchronized groups on the Groups page. (Optional) Step 3: Conﬁgure user attributes in PingFederate for access control in IAM Identity Center This is an optional procedure for PingFederate if you choose to conﬁgure attributes you will use in IAM Identity Center to manage access to your AWS resources. The attributes that you deﬁne in PingFederate are passed in a SAML assertion to IAM Identity Center. You will then create a permission set in IAM Identity Center to manage access based on the attributes you passed from PingFederate. Before you begin this procedure, you must ﬁrst enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. To conﬁgure user attributes in PingFederate for access control in IAM Identity Center 1. Sign on to the PingFederate administrative console. 2. Choose Applications from the top of the page, then click SP Connections. 3. Locate the application you created previously to form your SAML connection with IAM Identity Center, and click on the connection name. 4. Choose Browser SSO from the dark navigation headings near the top of the page. Then click on Conﬁgure Browser SSO. 5. On the Conﬁgure Browser SSO page, choose Assertion Creation, and then click on Conﬁgure Assertion Creation. 6. On the Conﬁgure Assertion Creation page, choose Attribute Contract. 7. On the Attribute Contract page, under Extend the Contract section, add a new attribute by performing the following steps: a. In the text box, enter https://aws.amazon.com/SAML/Attributes/ AccessControl:AttributeName, replace AttributeName with the name of the attribute you are expecting in IAM Identity Center. For example, https:// aws.amazon.com/SAML/Attributes/AccessControl:Department. b. For Attribute Name Format, choose urn:oasis:names:tc:SAML:2.0:attrname-format:uri. PingFederate 97 AWS IAM Identity Center User Guide c. Choose Add, and then choose Next. 8. On the Authentication Source Mapping page, choose the Adapter Instance conﬁgured with your application. 9. On the Attribute Contract Fulﬁllment page, choose the Source (data store) and Value (data store attribute) for the Attribute Contract https://aws.amazon.com/SAML/Attributes/ AccessControl:Department. Note If you have not yet conﬁgured a data source, you will need to do so now. See the Ping product documentation for information on how to choose and conﬁgure a data source in PingFederate. 10. Click Next repeatedly until you arrive on the Activation & Summary page, and then click Save. (Optional) Passing attributes for access control You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the
sso-ug-044	sso-ug.pdf	44	in PingFederate. 10. Click Next repeatedly until you arrive on the Activation & Summary page, and then click Save. (Optional) Passing attributes for access control You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. Troubleshooting For general SCIM and SAML troubleshooting with PingFederate, see the following sections: PingFederate 98 AWS IAM Identity Center User Guide • Speciﬁc users fail to synchronize into IAM Identity Center from an external SCIM provider • Issues regarding contents of SAML assertions created by IAM Identity Center • Duplicate user or group error when provisioning users or groups with an external identity provider • For more information on PingFederate, see PingFederate documentation. The following resources can help you troubleshoot as you work with AWS: • AWS re:Post - Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support PingOne IAM Identity Center supports automatic provisioning (synchronization) of user information from the PingOne product by Ping Identity (hereafter “Ping”) into IAM Identity Center. This provisioning uses the System for Cross-domain Identity Management (SCIM) v2.0 protocol. You conﬁgure this connection in PingOne using your IAM Identity Center SCIM endpoint and access token. When you conﬁgure SCIM synchronization, you create a mapping of your user attributes in PingOne to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and PingOne. The following steps walk you through how to enable automatic provisioning of users from PingOne to IAM Identity Center using the SCIM protocol. Note Before you begin deploying SCIM, we recommend that you ﬁrst review the Considerations for using automatic provisioning. Then continue reviewing additional considerations in the next section. Topics • Prerequisites • Considerations • Step 1: Enable provisioning in IAM Identity Center PingOne 99 AWS IAM Identity Center User Guide • Step 2: Conﬁgure provisioning in PingOne • (Optional) Step 3: Conﬁgure user attributes in PingOne for access control in IAM Identity Center • (Optional) Passing attributes for access control • Troubleshooting Prerequisites You'll need the following before you can get started: • A PingOne subscription or free trial, with both federated authentication and provisioning capabilities. For more information about how to obtain a free trial, see the Ping Identity website. • An IAM Identity Center-enabled account (free). For more information, see Enable IAM Identity Center. • The PingOne IAM Identity Center application added to your PingOne admin portal. You can obtain the PingOne IAM Identity Center application from the PingOne Application Catalog. For general information, see Add an application from the Application Catalog on the Ping Identity website. • A SAML connection from your PingOne instance to IAM Identity Center. After the PingOne IAM Identity Center application has been added to your PingOne admin portal, you must use it to conﬁgure a SAML connection from your PingOne instance to IAM Identity Center. Use the “download” and “import" metadata feature on both ends to exchange SAML metadata between PingOne and IAM Identity Center. For instructions on how to conﬁgure this connection, see the PingOne documentation. Considerations The following are important considerations about PingOne that can aﬀect how you implement provisioning with IAM Identity Center. • PingOne does not support provisioning of groups through SCIM. Contact Ping for the latest information on group support in SCIM for PingOne. • Users may continue to be provisioned from PingOne after disabling provisioning in the PingOne admin portal. If you need to terminate provisioning immediately, delete the relevant SCIM bearer token, and/or disable Provisioning an external identity provider into IAM Identity Center using SCIM in IAM Identity Center. PingOne 100 AWS IAM Identity Center User Guide • If an attribute for a user is removed from the data store conﬁgured in PingOne, that attribute will not be removed from the corresponding user in IAM Identity Center. This is a known limitation in PingOne’s provisioner implementation. If an attribute is modiﬁed, the change will be synchronized to IAM Identity Center. • The following are important notes regarding your SAML conﬁguration in PingOne: • IAM Identity Center supports only emailaddress as a NameId format. This means you need to choose a user attribute that is unique within your directory in
sso-ug-045	sso-ug.pdf	45	PingOne 100 AWS IAM Identity Center User Guide • If an attribute for a user is removed from the data store conﬁgured in PingOne, that attribute will not be removed from the corresponding user in IAM Identity Center. This is a known limitation in PingOne’s provisioner implementation. If an attribute is modiﬁed, the change will be synchronized to IAM Identity Center. • The following are important notes regarding your SAML conﬁguration in PingOne: • IAM Identity Center supports only emailaddress as a NameId format. This means you need to choose a user attribute that is unique within your directory in PingOne, non-null, and formatted as an email/UPN (for example, [email protected]) for your SAML_SUBJECT mapping in PingOne. Email (Work) is a reasonable value to use for test conﬁgurations with the PingOne built-in directory. • Users in PingOne with an email address containing a + character may be unable to sign in to IAM Identity Center, with errors such as 'SAML_215' or 'Invalid input'. To ﬁx this, in PingOne, choose the Advanced option for the SAML_SUBJECT mapping in Attribute Mappings. Then set Name ID Format to send to SP: to urn:oasis:names:tc:SAML:1.1:nameid- format:emailAddress in the drop-down menu. Step 1: Enable provisioning in IAM Identity Center In this ﬁrst step, you use the IAM Identity Center console to enable automatic provisioning. To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. PingOne 101 AWS IAM Identity Center User Guide Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in your IdP later in this tutorial. 5. Choose Close. Now that you have set up provisioning in the IAM Identity Center console, you need to complete the remaining tasks using the PingOne IAM Identity Center application. These steps are described in the following procedure. Step 2: Conﬁgure provisioning in PingOne Use the following procedure in the PingOne IAM Identity Center application to enable provisioning with IAM Identity Center. This procedure assumes that you have already added the PingOne IAM Identity Center application to your PingOne admin portal. If you have not yet done so, refer to Prerequisites, and then complete this procedure to conﬁgure SCIM provisioning. To conﬁgure provisioning in PingOne 1. Open the PingOne IAM Identity Center application that you installed as part of conﬁguring SAML for PingOne (Applications > My Applications). See Prerequisites. 2. Scroll to the bottom of the page. Under User Provisioning, choose the complete link to navigate to the user provisioning conﬁguration of your connection. 3. On the Provisioning Instructions page, choose Continue to Next Step. 4. In the previous procedure, you copied the SCIM endpoint value in IAM Identity Center. Paste that value into the SCIM URL ﬁeld in the PingOne IAM Identity Center application. Also, in the previous procedure you copied the Access token value in IAM Identity Center. Paste that value into the ACCESS_TOKEN ﬁeld in the PingOne IAM Identity Center application. 5. For REMOVE_ACTION, choose either Disabled or Deleted (see the description text on the page for more details). 6. On the Attribute Mapping page, choose a value to use for the SAML_SUBJECT (NameId) assertion, following guidance from Considerations earlier on this page. Then choose Continue to Next Step. PingOne 102 AWS IAM Identity Center User Guide 7. On the PingOne App Customization - IAM Identity Center page, make any desired customization changes (optional), and click Continue to Next Step. 8. On the Group Access page, choose the groups containing the users you would like to enable for provisioning and single sign-on to IAM Identity Center. Choose Continue to Next Step. 9. Scroll to the bottom of the page, and choose Finish to start provisioning. 10. To verify that users have been successfully synchronized to IAM Identity Center, return to the IAM Identity Center console and choose Users. Synchronized users from PingOne will appear on the Users page. These users can now be assigned to accounts and applications within IAM Identity Center. Remember that PingOne does not support provisioning of groups or group memberships through SCIM. Contact Ping for more information. (Optional) Step 3: Conﬁgure user attributes in PingOne for access
sso-ug-046	sso-ug.pdf	46	sign-on to IAM Identity Center. Choose Continue to Next Step. 9. Scroll to the bottom of the page, and choose Finish to start provisioning. 10. To verify that users have been successfully synchronized to IAM Identity Center, return to the IAM Identity Center console and choose Users. Synchronized users from PingOne will appear on the Users page. These users can now be assigned to accounts and applications within IAM Identity Center. Remember that PingOne does not support provisioning of groups or group memberships through SCIM. Contact Ping for more information. (Optional) Step 3: Conﬁgure user attributes in PingOne for access control in IAM Identity Center This is an optional procedure for PingOne if you choose to conﬁgure attributes for IAM Identity Center to manage access to your AWS resources. The attributes that you deﬁne in PingOne is passed in a SAML assertion to IAM Identity Center. You then create a permission set in IAM Identity Center to manage access based on the attributes you passed from PingOne. Before you begin this procedure, you must ﬁrst enable the Attributes for access control feature. For more information about how to do this, see Enable and conﬁgure attributes for access control. To conﬁgure user attributes in PingOne for access control in IAM Identity Center 1. Open the PingOne IAM Identity Center application that you installed as part of conﬁguring SAML for PingOne (Applications > My Applications). 2. Choose Edit, and then choose Continue to Next Step until you get to the Attribute Mappings page. 3. On the Attribute Mappings page, choose Add new attribute, and then do the following. You must perform these steps for each attribute you will add for use in IAM Identity Center for access control. a. In the Application Attribute ﬁeld, enter https://aws.amazon.com/SAML/ Attributes/AccessControl:AttributeName. Replace AttributeName with the PingOne 103 AWS IAM Identity Center User Guide name of the attribute you are expecting in IAM Identity Center. For example, https:// aws.amazon.com/SAML/Attributes/AccessControl:Email. b. In the Identity Bridge Attribute or Literal Value ﬁeld, choose user attributes from your PingOne directory. For example, Email (Work). 4. Choose Next a few times, and then choose Finish. (Optional) Passing attributes for access control You can optionally use the Attributes for access control feature in IAM Identity Center to pass an Attribute element with the Name attribute set to https://aws.amazon.com/SAML/ Attributes/AccessControl:{TagKey}. This element allows you to pass attributes as session tags in the SAML assertion. For more information about session tags, see Passing session tags in AWS STS in the IAM User Guide. To pass attributes as session tags, include the AttributeValue element that speciﬁes the value of the tag. For example, to pass the tag key-value pair CostCenter = blue, use the following attribute. <saml:AttributeStatement> <saml:Attribute Name="https://aws.amazon.com/SAML/Attributes/AccessControl:CostCenter"> <saml:AttributeValue>blue </saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> If you need to add multiple attributes, include a separate Attribute element for each tag. Troubleshooting For general SCIM and SAML troubleshooting with PingOne, see the following sections: • Speciﬁc users fail to synchronize into IAM Identity Center from an external SCIM provider • Issues regarding contents of SAML assertions created by IAM Identity Center • Duplicate user or group error when provisioning users or groups with an external identity provider • For more information on PingOne, see PingOne documentation. The following resources can help you troubleshoot as you work with AWS: PingOne 104 AWS IAM Identity Center User Guide • AWS re:Post - Find FAQs and links to other resources to help you troubleshoot issues. • AWS Support - Get technical support Conﬁgure user access with the default IAM Identity Center directory When you enable IAM Identity Center for the ﬁrst time, it's automatically conﬁgured with an Identity Center directory as your default identity source, so you don't need to choose an identity source. If your organization uses another identity provider such as Microsoft Active Directory, Microsoft Entra ID, or Okta consider integrating that identity source with IAM Identity Center instead of using the default conﬁguration. Objective In this tutorial, you'll use the default directory as your identity source and an IAM Identity Center organization instance to set up and test an administrative user. This administrative user creates and manages users and groups and grants AWS access with permission sets. In the next steps, you'll create the following: • An administrative user named Nikki Wolf • A group named Admin team • A permission set named AdminAccess To verify everything was created correctly, you'll sign in and set the administrative user's password. After completing this tutorial, you can use the administrative user to add more users in IAM Identity Center, create additional permission sets, and set up organizational access to applications. Alternatively, if you want to grant users access to application, you can follow step 1 of this procedure and conﬁgure application access. Prerequisites The following prerequisites are needed to complete this
sso-ug-047	sso-ug.pdf	47	next steps, you'll create the following: • An administrative user named Nikki Wolf • A group named Admin team • A permission set named AdminAccess To verify everything was created correctly, you'll sign in and set the administrative user's password. After completing this tutorial, you can use the administrative user to add more users in IAM Identity Center, create additional permission sets, and set up organizational access to applications. Alternatively, if you want to grant users access to application, you can follow step 1 of this procedure and conﬁgure application access. Prerequisites The following prerequisites are needed to complete this tutorial: • Enable IAM Identity Center and have an organization instance of IAM Identity Center. • If you have an account instance of IAM Identity Center, you can create users and groups as well as grant them access to applications. For more information, see Application access. Identity Center directory 105 AWS IAM Identity Center User Guide • Sign in to the AWS Management Console and access the IAM Identity Center console either as a: • New to AWS (root user) – Sign in as the account owner by choosing AWS account root user and entering your AWS account email address. On the next page, enter your password. • Already using AWS (IAM credentials) – Sign in using your IAM credentials with administrative permissions. • For more help signing in to the AWS Management Console, see AWS Sign-In Guide. • You can conﬁgure multi-factor authentication for your IAM Identity Center users. For more information, see Conﬁgure MFA in IAM Identity Center. Step 1: Add a user 1. Open the IAM Identity Center console. 2. In the IAM Identity Center navigation pane, choose Users, then select Add user. 3. On the Specify user details page, complete the following information: • Username - For this tutorial, enter nikkiw. When creating users, choose usernames that are easy to remember. Your users must remember the username to sign in to the AWS access portal and you can't change it later. • Password - Choose Send an email to this user with password setup instructions (Recommended). This option sends the user an email addressed from Amazon Web Services, with the subject line Invitation to join IAM Identity Center. The email comes from either no- [email protected] or [email protected]. Add these email addresses to your approved senders list. • Email address - Enter an email address for the user where you can receive the email. Then, enter it again to conﬁrm it. Each user must have a unique email address. • First name - Enter the ﬁrst name for the user. For this tutorial, enter Nikki. • Last name - Enter the last name for the user. For this tutorial, enter Wolf. • Display name - The default value is the ﬁrst and last name of the user. If you want to change the display name, you can enter something diﬀerent. The display name is visible in the sign-in portal and users list. • Complete the optional information if desired. It isn’t used during this tutorial and you can change it later. Identity Center directory 106 AWS IAM Identity Center User Guide 4. Choose Next. The Add user to groups page appears. We're going to create a group to assign administrative permissions to instead of giving them directly to Nikki. Choose Create group A new browser tab opens to display the Create group page. a. Under Group details, in Group name enter a name for the group. We recommend a group name that identiﬁes the role of the group. For this tutorial, enter Admin team. b. Choose Create group c. Close the Groups browser tab to return to the Add user browser tab 5. In the Groups area, select the Refresh button. The Admin team group appears in the list. Select the checkbox next to Admin team, and then choose Next. 6. On the Review and add user page, conﬁrm the following: • Primary information appears as you intended • Groups shows the user added to the group you created If you want to make changes, choose Edit. When all details are correct choose Add user. A notiﬁcation message informs you that the user was added. Next, you'll add administrative permissions for the Admin team group so that Nikki has access to resources. Step 2: Add administrative permissions 1. In the IAM Identity Center navigation pane, under Multi-account permissions, choose AWS accounts. 2. On the AWS accounts page the Organizational structure displays your organization with your accounts underneath it in the hierarchy. Select the checkbox for your management account, then select Assign users or groups. 3. The Assign users and groups workﬂow displays. It consists of three steps: a. For Step 1: Select users and groups choose the Admin team group you created. Then choose Next. Identity Center
sso-ug-048	sso-ug.pdf	48	add administrative permissions for the Admin team group so that Nikki has access to resources. Step 2: Add administrative permissions 1. In the IAM Identity Center navigation pane, under Multi-account permissions, choose AWS accounts. 2. On the AWS accounts page the Organizational structure displays your organization with your accounts underneath it in the hierarchy. Select the checkbox for your management account, then select Assign users or groups. 3. The Assign users and groups workﬂow displays. It consists of three steps: a. For Step 1: Select users and groups choose the Admin team group you created. Then choose Next. Identity Center directory 107 AWS IAM Identity Center User Guide b. For Step 2: Select permission sets choose Create permission set to open a new tab that steps you through the three sub-steps involved in creating a permission set. i. For Step 1: Select permission set type complete the following: • In Permission set type, choose Predeﬁned permission set. • In Policy for predeﬁned permission set, choose AdministratorAccess. Choose Next. ii. For Step 2: Specify permission set details, keep the default settings, and choose Next. The default settings create a permission set named AdministratorAccess with session duration set to one hour. You can change the name of the permission set by entering a new name in the Permission set name ﬁeld. iii. For Step 3: Review and create, verify that the Permission set type uses the AWS managed policy AdministratorAccess. Choose Create. On the Permission sets page a notiﬁcation appears informing you that the permission set was created. You can close this tab in your web browser now. On the Assign users and groups browser tab, you are still on Step 2: Select permission sets from which you started the create permission set workﬂow. In the Permissions sets area, choose the Refresh button. The AdministratorAccess permission set you created appears in the list. Select the check box for that permission set and then choose Next. c. On the Step 3: Review and submit assignments page, conﬁrm that the Admin team group is selected and that the AdministratorAccess permission set is selected, then choose Submit. The page updates with a message that your AWS account is being conﬁgured. Wait until the process completes. You are returned to the AWS accounts page. A notiﬁcation message informs you that your AWS account has been reprovisioned and the updated permission set applied. Identity Center directory 108 AWS IAM Identity Center User Guide Congratulations! You have successfully set up your ﬁrst user, group, and permission set. In the next portion of this tutorial you'll test Nikki's access by signing in to the AWS access portal with their administrative credentials and set their password. Sign out of the console now. Step 3: Test user access Now that Nikki Wolf is a user in your organization, they can sign in and access the resources to which they're granted permission according to their permission set. To verify that the user is correctly conﬁgured, in this next step you'll use Nikki's credentials to sign in and set up their password. When you added the user Nikki Wolf in Step 1 you chose to have Nikki receive an email with password setup instructions. It's time to open that email and do the following: 1. In the email, select the Accept invitation link to accept the invitation. Note The email also includes Nikki's user name and the AWS access portal URL that they'll use to sign in to the organization. Record this information for future use. You are taken to the New user sign up page where you can set Nikki's password and register their MFA device. 2. After setting Nikki's password, you are navigated to the Sign in page. Enter nikkiw and choose Next, then enter Nikki's password and choose Sign in. 3. The AWS access portal opens displaying the organization and applications you can access. Select the organization to expand it into a list of AWS accounts then select the account to display the roles that you can use to access resources in the account. Each permission set has two management methods you can use, either Role or Access keys. • Role, for example AdministratorAccess - Opens the AWS Console Home. • Access keys - Provides credentials that you can use with the AWS CLI or and AWS SDK. Includes the information for using either short-term credentials that automatically refresh Identity Center directory 109 AWS IAM Identity Center User Guide or short-term access keys. For more information, see Getting IAM Identity Center user credentials for the AWS CLI or AWS SDKs. 4. Choose the Role link to sign in to the AWS Console Home. You are signed in and navigated to the AWS Console Home page. Explore the console and conﬁrm that you have the access you expected. Next steps Now
sso-ug-049	sso-ug.pdf	49	• Access keys - Provides credentials that you can use with the AWS CLI or and AWS SDK. Includes the information for using either short-term credentials that automatically refresh Identity Center directory 109 AWS IAM Identity Center User Guide or short-term access keys. For more information, see Getting IAM Identity Center user credentials for the AWS CLI or AWS SDKs. 4. Choose the Role link to sign in to the AWS Console Home. You are signed in and navigated to the AWS Console Home page. Explore the console and conﬁrm that you have the access you expected. Next steps Now that you've created an administrative user in IAM Identity Center, you can: • Assign applications • Add other users • Assign users to accounts • Conﬁgure additional permission sets Note You can assign multiple permission sets to the same user. To follow the best practice of applying least-privilege permissions, after you create your administrative user, create a more restrictive permission set and assign it to the same user. That way, you can access your AWS account with only the permissions that you require, rather than administrative permissions. After your users accept their invitation to activate their account and they sign into the AWS access portal, the only items that appear in the portal are for the AWS accounts, roles, and applications to which they're assigned. Video tutorials As an additional resource, you can use these video tutorials to learn more about setting up external identity providers: • Migrating between external identity providers in AWS IAM Identity Center • Federating your existing AWS IAM Identity Center instance with Microsoft Entra ID Video tutorials 110 AWS IAM Identity Center User Guide Authentication in IAM Identity Center A user signs in to the AWS access portal using their user name. When they do, IAM Identity Center redirects the request to the IAM Identity Center authentication service based on the directory associated with the user email address. Once authenticated, users have single sign-on access to any of the AWS accounts and third-party software-as-a-service (SaaS) applications that show up in the portal without additional sign-in prompts. This means that users no longer need to keep track of multiple account credentials for the various assigned AWS applications that they use on a daily basis. Authentication sessions There are two types of authentication sessions maintained by IAM Identity Center: one to represent the users’ sign in to IAM Identity Center, and another to represent the users’ access to AWS managed applications, such as Amazon SageMaker AI Studio or Amazon Managed Grafana. Each time a user signs in to IAM Identity Center, a sign in session is created for the duration conﬁgured in IAM Identity Center, which can be up to 90 days. For more information, see Conﬁgure the session duration of the AWS access portal and IAM Identity Center integrated applications. Each time the user accesses an application, the IAM Identity Center sign in session is used to create an IAM Identity Center application session for that application. IAM Identity Center application sessions have a refreshable 1-hour lifetime – that is, IAM Identity Center application sessions are automatically refreshed every hour as long as the IAM Identity Center sign in session from which they were obtained is still valid. If the user signs out using the AWS access portal, the user's sign in session ends. The next time application refreshes its session, the application session will end. When the user uses IAM Identity Center to access the AWS Management Console or AWS CLI, the IAM Identity Center sign in session is used to obtain an IAM session, as speciﬁed in the corresponding IAM Identity Center permission set (more speciﬁcally, IAM Identity Center assumes an IAM role, which IAM Identity Center manages, in the target account). IAM sessions persist for the time speciﬁed for the permission set, unconditionally. Note IAM Identity Center does not support SAML Single Logout initiated by an identity provider that acts as your identity source, and it does not send SAML Single Logout to SAML applications that use IAM Identity Center as an Identity provider. Authentication sessions 111 AWS IAM Identity Center User Guide When you disable or delete a user in IAM Identity Center, that user will immediately be prevented from signing in to create new IAM Identity Center sign in sessions. When you revoke a user sign-in session, the user must sign-in again. When an IAM Identity Center administrator deletes or disables a user, the user will immediately lose access to the AWS access portal. Existing application sessions will lose access within 30 minutes following deletion or being disabled. In some cases, it can take up to 1 hour for existing applications to lose access. Any existing IAM role sessions will continue based on the duration conﬁgured in the IAM Identity Center
sso-ug-050	sso-ug.pdf	50	Center, that user will immediately be prevented from signing in to create new IAM Identity Center sign in sessions. When you revoke a user sign-in session, the user must sign-in again. When an IAM Identity Center administrator deletes or disables a user, the user will immediately lose access to the AWS access portal. Existing application sessions will lose access within 30 minutes following deletion or being disabled. In some cases, it can take up to 1 hour for existing applications to lose access. Any existing IAM role sessions will continue based on the duration conﬁgured in the IAM Identity Center permission set which can be conﬁgured up to 12 hours. This behavior also applies when a user session is revoked or the user signs out. The following table summarizes IAM Identity Center behaviors: User experience / system behavior Time after user disabled / deleted Time after user session revoked / signs out User can no longer sign in IAM Identity Center User can no longer start new application or IAM role sessions via IAM Identity Center User can no longer access any applications (all application sessions are terminated by the administrator or the user signs out) User can no longer access any AWS accounts through IAM Identity Center Eﬀective immediately Not applicable Eﬀective immediately Eﬀective immediately Up to 30 minutes * Up to 30 minutes * Up to 12 hours (up to 1 hour for IAM Identity Center sign in session expiry, plus up to 12 hours for administrator-conf igured IAM role session expiry Up to 12 hours (up to 1 hour for IAM Identity Center sign in session expiry, plus up to 12 hours for administrator-conf igured IAM role session expiry per the IAM Identity Center per the IAM Identity Center Authentication sessions 112 AWS IAM Identity Center User Guide User experience / system behavior Time after user disabled / deleted Time after user session revoked / signs out session duration settings for session duration settings for the permission set) the permission set) * In some cases, for example service disruption, it can take up to an hour to lose application access. For more information about sessions, see Set session duration for AWS accounts. Revoke access for deleted users To immediately revoke access to make authorized API calls when an IAM Identity Center user is either disabled or deleted, you can: 1. Add or update the inline policy of the permission set(s) assigned to the user by adding an explicit Deny eﬀect for all actions on all resources. 2. Specify the aws:userid or identitystore:userid condition key. Alternatively, you can use a Service Control Policy to revoke the user's access across all member accounts in your organization. Example SCPs to revoke access { "Version": "2012-10-17", "Statement" : [ { "Effect": "Deny", "Action": "", "Resource": "", "Condition": { "StringLike": { "aws:UserId": ":[email protected]" } } } ] } Revoke access for deleted users 113 AWS IAM Identity Center User Guide { "Version": "2012-10-17", "Statement" : [ { "Effect": "Deny", "Action": "", "Resource": "*", "Condition": { "StringEquals": { "identitystore:UserId": "DELETEDUSER_ID" } } } ] } Revoke access for deleted users 114 AWS IAM Identity Center User Guide Connect workforce users IAM Identity Center is the AWS solution for connecting your workforce users to AWS managed applications such as Amazon Q Developer and Amazon QuickSight, and other AWS resources. You can connect your existing identity provider and synchronize users and groups from your directory, or create and manage your users directly in IAM Identity Center. Already using IAM for access to AWS accounts? You don’t need to make any changes to your current AWS account workﬂows to use IAM Identity Center for access to AWS managed applications. If you’re using federation with IAM or IAM users for AWS account access, your users can continue to access AWS accounts in the same way they always have, and you can continue to use your existing workﬂows to manage that access. Topics • IAM Identity Center use cases • Users, groups, and provisioning in IAM Identity Center • Manage your identity source • Using the AWS access portal • Multi-factor authentication for Identity Center users IAM Identity Center use cases Learn how to use IAM Identity Center to centrally manage user access and permissions across multiple AWS accounts and various AWS managed and customer managed applications Use case Learn more Use IAM Identity Center to grant application access and administrative permissions to users and groups within an organization. Enable single sign-on access to your AWS applications (Application admin role) Use IAM Identity Center to centrally manage access and permissions for AWS managed and Application access customer managed applications. Use cases 115 AWS IAM Identity Center Use case Use IAM Identity Center to centrally manage access and permissions across multiple AWS accounts within an organization. Learn more AWS
sso-ug-051	sso-ug.pdf	51	to centrally manage user access and permissions across multiple AWS accounts and various AWS managed and customer managed applications Use case Learn more Use IAM Identity Center to grant application access and administrative permissions to users and groups within an organization. Enable single sign-on access to your AWS applications (Application admin role) Use IAM Identity Center to centrally manage access and permissions for AWS managed and Application access customer managed applications. Use cases 115 AWS IAM Identity Center Use case Use IAM Identity Center to centrally manage access and permissions across multiple AWS accounts within an organization. Learn more AWS account access User Guide Enable single sign-on access to your AWS applications (Application admin role) This use case provides guidance if you're an application administrator who manages AWS managed applications such as Amazon SageMaker AI or AWS IoT SiteWise, and you must provide single sign- on access to your users. Before you get started, consider the following: • Do you want to create a test or production environment in a separate organization in AWS Organizations? • Is IAM Identity Center already enabled in your organization? Do you have permissions to enable IAM Identity Center in the management account of AWS Organizations? Review the following guidance to determine next steps based on your business needs. Conﬁgure my AWS application in a standalone AWS account If you must provide single sign-on access to an AWS application and know that your IT department does not yet use IAM Identity Center, you might need to create a standalone AWS account to get started. By default, when you create your own AWS account, you'll have the permissions that you require to create and manage your own AWS organization. To enable IAM Identity Center, you must have AWS account root user permissions. IAM Identity Center and AWS Organizations can be enabled automatically during setup for some AWS applications (for example, Amazon Managed Grafana). If your AWS application doesn't provide the option to enable these services, you must set up AWS Organizations and IAM Identity Center before you can provide single sign-on access to your application. Enable single sign-on access to your AWS applications 116 AWS IAM Identity Center User Guide IAM Identity Center isn't conﬁgured in my organization In your role as an application administrator, you might not be able to enable IAM Identity Center, depending on your permissions. IAM Identity Center requires speciﬁc permissions in the AWS Organizations management account. In this case, contact the appropriate administrator to have IAM Identity Center enabled in the Organizations management account. If you do have suﬃcient permissions to enable IAM Identity Center, do this ﬁrst, then proceed with the application setup. For more information, see Getting started with IAM Identity Center. IAM Identity Center is currently conﬁgured in my organization In this scenario, you can continue to deploy your AWS application without taking any further action. Note If your organization enabled IAM Identity Center in the management account before November 25th, 2019, you must also enable AWS managed applications in the management account and optionally in the member accounts. If you enable them in the management account only, you can enable them in member accounts later. To enable these applications, choose Enable access in the IAM Identity Center console's Settings page in the AWS managed applications section. For more information, see Sharing identity information . Users, groups, and provisioning in IAM Identity Center IAM Identity Center enables you to control who can sign in and what resources they can access. A user must be provisioned to sign in. You can then assign access only to provisioned users or groups. Learn about provisioning users and groups, whether sourced from an external identity provider or created directly in IAM Identity Center. Username and email address uniqueness IAM Identity Center requires each user have a unique username. The username is the user’s primary identiﬁer. The username does not have to match the user’s email address. IAM Identity Center requires that all usernames and email addresses for your users are non-NULL and unique. Users, groups, and provisioning 117 AWS IAM Identity Center Groups User Guide Groups are a logical combination of users that you deﬁne. You can create groups and add users to the groups. IAM Identity Center doesn't support nested groups (A group within a group). Groups are useful when assigning access to AWS accounts and applications. Rather than assign each user individually, you give permissions to a group. Later, as you add or remove users from a group, the user dynamically gets or loses access to accounts and applications that you assigned to the group. User and group provisioning Provisioning is the process of making user and group information available for use by IAM Identity Center and AWS managed applications or customer managed applications. You can create users and groups
sso-ug-052	sso-ug.pdf	52	to the groups. IAM Identity Center doesn't support nested groups (A group within a group). Groups are useful when assigning access to AWS accounts and applications. Rather than assign each user individually, you give permissions to a group. Later, as you add or remove users from a group, the user dynamically gets or loses access to accounts and applications that you assigned to the group. User and group provisioning Provisioning is the process of making user and group information available for use by IAM Identity Center and AWS managed applications or customer managed applications. You can create users and groups directly in IAM Identity Center or connect your identity source to IAM Identity Center. With IAM Identity Center, you're able to assign users and groups access to connected applications and AWS accounts. Provisioning in IAM Identity Center varies based on the identity source that you use. For more information, see Manage your identity source. User and group deprovisioning Deprovisioning is the process of removing users and group information from IAM Identity Center. If you’re using Active Directory or an external identity provider with IAM Identity Center, you should remove users and groups from these identity sources rather than IAM Identity Center. Deleting IAM Identity Center users and groups will not completely remove them if your identity source is Active Directory or an external identity provider. If you’ve conﬁgured automatic provisioning of the users in your IdP to IAM Identity Center, these previously deleted users and groups will be reprovisioned in IAM Identity Center. If you need to deprovision IAM Identity Center users or groups, you should ﬁrst remove any assignments of permission sets or applications to the users or groups you want to deprovision. Otherwise, you’ll have unassigned permission sets and application assignments in your IAM Identity Center. Groups 118 AWS IAM Identity Center User Guide Manage your identity source Your identity source in IAM Identity Center deﬁnes where your users and groups are managed. After you conﬁgure your identity source, you can look up users or groups to grant them single sign- on access to AWS accounts, applications, or both. You can have only one identity source per organization in AWS Organizations. You can choose one of the following as your identity source: • External identity provider – Choose this option if you want to manage users in an external identity provider (IdP) such as Okta or Microsoft Entra ID. • Active Directory – Choose this option if you want to continue managing users in either your AWS Managed Microsoft AD directory using AWS Directory Service or your self-managed directory in Active Directory (AD). • Identity Center directory – When you enable IAM Identity Center for the ﬁrst time, it's automatically conﬁgured with an Identity Center directory as your default identity source unless you choose a diﬀerent identity source. With the Identity Center directory, you create your users and groups, and assign their level of access to your AWS accounts and applications. Note IAM Identity Center does not support SAMBA4-based Simple AD as an identity source. Topics • Considerations for changing your identity source • Change your identity source • Manage sign-in and attribute use for all identity source types • Manage identities in IAM Identity Center • Connect to a Microsoft AD directory • Manage an external identity provider Manage your identity source 119 AWS IAM Identity Center User Guide Considerations for changing your identity source Although you can change your identity source at any time, we recommend that you consider how this change might aﬀect your current deployment. If you're already managing users and groups in one identity source, changing to a diﬀerent identity source might remove all user and group assignments that you conﬁgured in IAM Identity Center. If this occurs, all users, including the administrative user in IAM Identity Center, will lose single sign- on access to their AWS accounts and applications. Before you change the identity source for IAM Identity Center, review the following considerations before you proceed. If you want to proceed with changing your identity source, see Change your identity source for more information. Changing between IAM Identity Center directory and Active Directory If you're already managing users and groups in Active Directory, we recommend that you consider connecting your directory when you enable IAM Identity Center and choose your identity source. Do this before you create any users and groups in the default Identity Center directory and make any assignments. If you're already managing users and groups in the default Identity Center directory, consider the following: • Assignments removed and users and groups deleted – Changing your identity source to Active Directory deletes your users and groups from the Identity Center directory. This change also removes your assignments. In this case, after you change to Active Directory, you must synchronize your
sso-ug-053	sso-ug.pdf	53	Directory, we recommend that you consider connecting your directory when you enable IAM Identity Center and choose your identity source. Do this before you create any users and groups in the default Identity Center directory and make any assignments. If you're already managing users and groups in the default Identity Center directory, consider the following: • Assignments removed and users and groups deleted – Changing your identity source to Active Directory deletes your users and groups from the Identity Center directory. This change also removes your assignments. In this case, after you change to Active Directory, you must synchronize your users and groups from Active Directory into the Identity Center directory, and then reapply their assignments. If you choose to not use Active Directory, you must create your users and groups in the Identity Center directory, and then make assignments. • Assignments aren't deleted when identities are deleted – When identities are deleted in the Identity Center directory, corresponding assignments also get deleted in IAM Identity Center. However in Active Directory, when identities are deleted (either in Active Directory or the synced identities), corresponding assignments aren't deleted. • No outbound synchronization for APIs – If you use Active Directory as your identity source, we recommend that you use the Create, Update, and Delete APIs with caution. IAM Identity Center Considerations for changing your identity source 120 AWS IAM Identity Center User Guide doesn't support outbound synchronization, so your identity source doesn't automatically update with the changes that you make to users or groups using these APIs. • Access portal URL will change – Changing your identity source between IAM Identity Center and Active Directory also changes the URL for the AWS access portal. • If users are deleted or disabled in the IAM Identity Center console using Identity Store APIs, users with active sessions can continue to access integrated applications and accounts. For information about authentication session duration and user behavior, see Authentication in IAM Identity Center. For information about how IAM Identity Center provisions users and groups, see Connect to a Microsoft AD directory. Changing from IAM Identity Center to an external IdP If you change your identity source from IAM Identity Center to an external identity provider (IdP), consider the following: • Assignments and memberships work with correct assertions – your user assignments, group assignments, and group memberships continue to work as long as the new IdP sends the correct assertions (for example, SAML nameIDs). These assertions must match the user names and groups in IAM Identity Center. • No outbound synchronization – IAM Identity Center doesn't support outbound synchronization, so your external IdP won't automatically update with changes to users and groups that you make in IAM Identity Center. • SCIM provisioning – if you are using SCIM provisioning, changes to users and groups in your identity provider reﬂect only in IAM Identity Center after your identity provider sends those changes to IAM Identity Center. See Considerations for using automatic provisioning. • Rollback – you can revert your identity source back to using IAM Identity Center at any time. See Changing from an external IdP to IAM Identity Center. • Existing user sessions are revoked on session duration expiry – Once you change your identity source to an external identity provider, active user sessions persist for the remainder of the maximum session duration conﬁgured in the console. For example, if the AWS access portal session duration is set to eight hours, and you changed the identity source in the fourth hour, active user sessions persist for an additional four hours. To revoke user sessions, see Delete active user sessions for the AWS access portal and AWS integrated applications. Considerations for changing your identity source 121 AWS IAM Identity Center User Guide • If users are deleted or disabled in the IAM Identity Center console using Identity Store APIs, users with active sessions can continue to access integrated applications and accounts. For information about authentication session duration and user behavior, see Authentication in IAM Identity Center. Note You won't be able to revoke user sessions from the IAM Identity Center console after you've deleted the user. For information about how IAM Identity Center provisions users and groups, see Manage an external identity provider. Changing from an external IdP to IAM Identity Center If you change your identity source from an external identity provider (IdP) to IAM Identity Center, consider the following: • IAM Identity Center preserves all your assignments. • Force password reset – Users who had passwords in IAM Identity Center can continue signing in with their old passwords. For users who were in the external IdP and weren't in IAM Identity Center, an administrator must force a password reset. • Existing user sessions are revoked on session duration expiry – Once you change your identity source
sso-ug-054	sso-ug.pdf	54	Manage an external identity provider. Changing from an external IdP to IAM Identity Center If you change your identity source from an external identity provider (IdP) to IAM Identity Center, consider the following: • IAM Identity Center preserves all your assignments. • Force password reset – Users who had passwords in IAM Identity Center can continue signing in with their old passwords. For users who were in the external IdP and weren't in IAM Identity Center, an administrator must force a password reset. • Existing user sessions are revoked on session duration expiry – Once you change your identity source to IAM Identity Center, active user sessions persist for the remaining duration of the maximum session duration conﬁgured in the console. For example, if the AWS access portal session duration is eight hours, and you changed the identity source at fourth hour, active user sessions continue to run for an additional four hours. To revoke user sessions, see Delete active user sessions for the AWS access portal and AWS integrated applications. • If users are deleted or disabled in the IAM Identity Center console using Identity Store APIs, users with active sessions can continue to access integrated applications and accounts. For information about authentication session duration and user behavior, see Authentication in IAM Identity Center. Considerations for changing your identity source 122 AWS IAM Identity Center Note User Guide You won't be able to revoke user sessions from the IAM Identity Center console after you've deleted the user. For information about how IAM Identity Center provisions users and groups, see Manage identities in IAM Identity Center. Changing from one external IdP to another external IdP If you're already using an external IdP as your identity source for IAM Identity Center and you change to a diﬀerent external IdP, consider the following: • Assignments and memberships work with correct assertions – IAM Identity Center preserves all of your assignments. The user assignments, group assignments, and group memberships continue to work as long as the new IdP sends the correct assertions (for example, SAML nameIDs). These assertions must match the user names in IAM Identity Center when your users authenticate through the new external IdP. • SCIM provisioning – If you are using SCIM for provisioning into IAM Identity Center, we recommend that you review the IdP-speciﬁc information in this guide and the documentation provided by the IdP to ensure that the new provider matches users and groups correctly when SCIM is enabled. • Existing user sessions are revoked on session duration expiry – Once you change your identity source to diﬀerent external identity provider, active user sessions persist for the remaining duration of the maximum session duration conﬁgured in the console. For example, if the AWS access portal session duration is eight hours, and you changed the identity source at fourth hour, active user sessions persist for an additional four hours. To revoke user sessions, see Delete active user sessions for the AWS access portal and AWS integrated applications. • If users are deleted or disabled in the IAM Identity Center console using Identity Store APIs, users with active sessions can continue to access integrated applications and accounts. For information about authentication session duration and user behavior, see Authentication in IAM Identity Center. Considerations for changing your identity source 123 AWS IAM Identity Center Note User Guide You won't be able to revoke user sessions from the IAM Identity Center console after you've deleted the user. For information about how IAM Identity Center provisions users and groups, see Manage an external identity provider. Changing between Active Directory and an external IdP If you change your identity source from an external IdP to Active Directory, or from Active Directory to an external IdP, consider the following: • Users, groups, and assignments are deleted – All users, groups, and assignments are deleted from IAM Identity Center. No user or group information is aﬀected in either the external IdP or Active Directory. • Provisioning users – If you change to an external IdP, you must conﬁgure IAM Identity Center to provision your users. Alternatively, you must manually provision the users and groups for the external IdP before you can conﬁgure assignments. • Create assignments and groups – If you change to Active Directory, you must create assignments with the users and groups that are in your directory in Active Directory. • If users are deleted or disabled in the IAM Identity Center console using Identity Store APIs, users with active sessions can continue to access integrated applications and accounts. For information about authentication session duration and user behavior, see Authentication in IAM Identity Center. For information about how IAM Identity Center provisions users and groups, see Connect to a Microsoft AD directory. Change your identity source The following procedure describes how to change from
sso-ug-055	sso-ug.pdf	55	and groups – If you change to Active Directory, you must create assignments with the users and groups that are in your directory in Active Directory. • If users are deleted or disabled in the IAM Identity Center console using Identity Store APIs, users with active sessions can continue to access integrated applications and accounts. For information about authentication session duration and user behavior, see Authentication in IAM Identity Center. For information about how IAM Identity Center provisions users and groups, see Connect to a Microsoft AD directory. Change your identity source The following procedure describes how to change from a directory that IAM Identity Center provides (the default Identity Center directory) to Active Directory or an external identity provider, or the other way around. Before you proceed, review the information in Considerations for changing your identity source. To complete this procedure, you'll need an Organization instance of Change your identity source 124 AWS IAM Identity Center User Guide IAM Identity Center. For more information, see Organization and account instances of IAM Identity Center. Warning Depending on your current deployment, this change removes any user and group assignments that you conﬁgured in IAM Identity Center. This change will also remove permission set IAM roles from your AWS accounts. As a result, you may need to update your resource policies, and should ensure this will not disrupt your access to AWS KMS keys and Amazon EKS clusters. To learn more, see Referencing permission sets in resource policies, Amazon EKS Cluster conﬁg maps, and AWS KMS key policies. When this occurs, all users and groups, including the administrative user in IAM Identity Center, will lose single sign-on access to their AWS accounts and applications. To change your identity source 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab. Choose Actions, and then choose Change identity source. 4. Under Choose identity source, select the source that you want to change to, and then choose Next. If you are changing to Active Directory, choose the available directory from the menu on the next page. Important Changing your identity source to or from Active Directory deletes users and groups from the Identity Center directory. This change also removes any assignments that you conﬁgured in IAM Identity Center. If you are switching to an external identity provider, we recommend that you follow the steps in How to connect to an external identity provider. 5. After you read the disclaimer and are ready to proceed, type ACCEPT. Change your identity source 125 AWS IAM Identity Center User Guide 6. Choose Change identity source. If you are changing your identity source to Active Directory, proceed to the next step. 7. Changing your identity source to Active Directory takes you to the Settings page. On the Settings page, do either of the following: • Choose Start guided setup. For information about how to complete the guided setup process, see Guided setup. • In the Identity source section, choose Actions, and then choose Manage sync to conﬁgure your sync scope, the list of users and groups to sync. Manage sign-in and attribute use for all identity source types IAM Identity Center enables administrators to control AWS access portal use, to set session durations for users in the AWS access portal and your applications, and to use attributes for access control. These capabilities work with an Identity Center directory or external identity provider as your identity source. Supported user and group attributes in IAM Identity Center Attributes are pieces of information that help you deﬁne and identify individual user or group objects, such as name, email, or members. IAM Identity Center supports most commonly used attributes regardless if they're entered manually during user creation or when automatically provisioned using a synchronization engine such as deﬁned in the System for Cross-Domain Identity Management (SCIM) speciﬁcation. • For more information about the System for Cross-Domain Identity Management (SCIM) speciﬁcation, see https://tools.ietf.org/html/rfc7642. • For more information about manual and automatic provisioning, see Provisioning when users come from an external IdP. • For more information about attribute mapping, see Attribute mappings between IAM Identity Center and External Identity Providers directory. Because IAM Identity Center supports SCIM for automatic provisioning use cases, the Identity Center directory supports all of the same user and group attributes that are listed in the SCIM speciﬁcation, with a few exceptions. The following sections describe which attributes aren't supported by IAM Identity Center. Manage sign-in and attribute use for all identity source types 126 AWS IAM Identity Center User objects User Guide All attributes from the SCIM user schema (https://tools.ietf.org/html/rfc7643#section-8.3) are supported in the IAM Identity Center identity store, except for the following: • password • ims • photos • entitlements • x509Certificates All sub-attributes for users are supported, except
sso-ug-056	sso-ug.pdf	56	supports SCIM for automatic provisioning use cases, the Identity Center directory supports all of the same user and group attributes that are listed in the SCIM speciﬁcation, with a few exceptions. The following sections describe which attributes aren't supported by IAM Identity Center. Manage sign-in and attribute use for all identity source types 126 AWS IAM Identity Center User objects User Guide All attributes from the SCIM user schema (https://tools.ietf.org/html/rfc7643#section-8.3) are supported in the IAM Identity Center identity store, except for the following: • password • ims • photos • entitlements • x509Certificates All sub-attributes for users are supported, except for the following: • 'display' sub-attribute of any multi-valued attribute (For example, emails or phoneNumbers) • 'version' sub-attribute of 'meta' attribute Group objects All attributes from the SCIM group schema (https://tools.ietf.org/html/rfc7643#section-8.4) are supported. All sub-attributes for groups are supported, except for the following: • 'display' sub-attribute of any multi-valued attribute (For example, members). Topics • Conﬁgure the session duration of the AWS access portal and IAM Identity Center integrated applications • Delete active user sessions for the AWS access portal and AWS integrated applications Conﬁgure the session duration of the AWS access portal and IAM Identity Center integrated applications The IAM Identity Center administrator can conﬁgure the session duration for both applications integrated with IAM Identity Center and the AWS access portal. The session duration of Manage sign-in and attribute use for all identity source types 127 AWS IAM Identity Center User Guide authentication into the AWS access portal and IAM Identity Center integrated applications is the maximum length of time that a user can be signed in without re-authenticating. The IAM Identity Center administrator can end an active AWS access portal session and by doing so also end the sessions of integrated applications. The default session duration is 8 hours. The IAM Identity Center administrator can specify a diﬀerent duration, from a minimum of 15 minutes to a maximum of 90 days. Custom duration value must be entered in minutes and be between 15 and 10080 minutes (7 days). For more information about authentication session duration and user behavior, see Authentication in IAM Identity Center. Note Modifying the AWS access portal session duration and ending the AWS access portal sessions have no eﬀect on the AWS Management Console session duration that you deﬁne in your permission sets. The following topics provide information about conﬁguring the session duration of the AWS access portal and IAM Identity Center integrated applications. Prerequisites and considerations The following are the prerequisites and considerations for conﬁguring the session duration for the AWS access portal and IAM Identity Center integrated applications. External identity providers IAM Identity Center uses SessionNotOnOrAfter attribute from SAML assertions to help determine how long the session can be valid for. • If SessionNotOnOrAfter is not passed in a SAML assertion, the duration of an AWS access portal session is not impacted by the duration of your external IdP session. For example, if your IdP session duration is 24 hours and you set an 18-hour session duration in IAM Identity Center, your users must re-authenticate in the AWS access portal after 18 hours. • If SessionNotOnOrAfter is passed in a SAML assertion, the session duration value is set to the shorter of the AWS access portal session duration and your SAML IdP session duration. If you set a 72-hour session duration in IAM Identity Center and your IdP has a session duration of 18 hours, your users will have access to AWS resources for the 18 hours deﬁned in your IdP. Manage sign-in and attribute use for all identity source types 128 AWS IAM Identity Center User Guide • If the session duration of your IdP is longer than the one set in IAM Identity Center, your users will be able to start a new IAM Identity Center session without re-entering their credentials, based on their still-valid login session with your IdP. AWS CLI and SDK sessions If you're using the AWS Command Line Interface, AWS Software Development Kits (SDKs), or other AWS development tools to access AWS services programmatically, the following prerequisites must be met to set session duration for the AWS access portal and the IAM Identity Center integrated applications. • You must conﬁgure the AWS access portal session duration in the IAM Identity Center console. • You must deﬁne a proﬁle for single sign-on settings in your shared AWS conﬁg ﬁle. This proﬁle is used to connect to the AWS access portal. We recommend that you use the SSO token provider conﬁguration. With this conﬁguration, your AWS SDK or tool can automatically retrieve refreshed authentication tokens. For more information, see SSO token provider conﬁguration in the AWS SDK and Tools Reference Guide. • Users must run a version of the AWS CLI or an SDK that supports session management. Minimum
sso-ug-057	sso-ug.pdf	57	You must conﬁgure the AWS access portal session duration in the IAM Identity Center console. • You must deﬁne a proﬁle for single sign-on settings in your shared AWS conﬁg ﬁle. This proﬁle is used to connect to the AWS access portal. We recommend that you use the SSO token provider conﬁguration. With this conﬁguration, your AWS SDK or tool can automatically retrieve refreshed authentication tokens. For more information, see SSO token provider conﬁguration in the AWS SDK and Tools Reference Guide. • Users must run a version of the AWS CLI or an SDK that supports session management. Minimum versions of the AWS CLI that support session management Following are the minimum versions of the AWS CLI that support session management. • AWS CLI V2 2.9 or later • AWS CLI V1 1.27.10 or later For information about how to install or update the latest AWS CLI version, see Installing or updating the latest version of the AWS CLI. If your users are running the AWS CLI, if you refresh your permission set just before the IAM Identity Center session is set to expire and the session duration is set to 20 hours while the permission set duration is set to 12 hours, the AWS CLI session runs for the maximum of 20 hours plus 12 hours for a total of 32 hours. For more information about the IAM Identity Center CLI, see AWS CLI Command Reference. Manage sign-in and attribute use for all identity source types 129 AWS IAM Identity Center User Guide Minimum versions of SDKs that support IAM Identity Center session management Following are the minimum versions of the SDKs that support IAM Identity Center session management. SDK Python PHP Ruby Java V2 Go V2 JS V2 JS V3 C++ .NET Topics Minimum version 1.26.10 3.245.0 aws-sdk-core 3.167.0 AWS SDK for Java v2 (2.18.13) Whole SDK: release-2022-11-11 and speciﬁc Go modules: credentials/v1.13.0, conﬁg/v1 .18.0 2.1253.0 v3.210.0 1.9.372 v3.7.400.0 • How to conﬁgure application session duration • How to extend the session duration for Amazon Q Developer How to conﬁgure application session duration IAM Identity Center administrators can extend session duration based on speciﬁc business needs, such as accommodating long-running tasks and minimizing the need for users to re-authenticate. Use the following procedure to conﬁgure the session duration of the AWS access portal and IAM Identity Center integrated applications. Manage sign-in and attribute use for all identity source types 130 AWS IAM Identity Center User Guide 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Authentication tab. 4. Under Authentication, next to Session settings, choose Conﬁgure. A Conﬁgure session settings dialog box appears. 5. In the Conﬁgure session settings dialog box, choose the maximum session duration in minutes, hours, and days for your users by selecting the drop down arrow. Choose a the length for the session, and then choose Save. You return to the Settings page. How to extend the session duration for Amazon Q Developer If your developers use Amazon Q Developer as part of an integrated development environment (IDE), you can set the session duration for Amazon Q Developer to 90 days. Depending on when you enabled IAM Identity Center, extended session duration for Amazon Q Developer might be enabled by default. This extended session doesn’t aﬀect the session duration of the AWS access portal or other IAM Identity Center integrated applications. Note Amazon Q Developer is accessible from consoles set to commercial AWS Regions that are enabled by default. If your IAM Identity Center instance is located in a Region where Amazon Q Developer isn’t currently accessible, enabling 90 day extended session duration won’t override the default setting. This means that your session duration remains unchanged, regardless of whether you enable 90 day extended session duration or not. For information, see Supported Regions for Amazon Q Developer. Enable or disable 90 day extended session duration for Amazon Q Developer. 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Authentication tab. 4. Under Authentication, next to Session settings, choose Conﬁgure. A Conﬁgure session settings dialog box appears. Manage sign-in and attribute use for all identity source types 131 AWS IAM Identity Center User Guide 5. In the Conﬁgure session settings dialog box, select the checkbox for Enable extended sessions for Amazon Q Developer. Deselect the checkbox to disable extended session duration. 6. Choose Save to return to the Settings page. Delete active user sessions for the AWS access portal and AWS integrated applications IAM Identity Center administrators can delete active user sessions. Deleting user sessions enables administrators to revoke access and remove stale sessions when users no longer require or shouldn’t maintain their current authentication state, such as when an employee leaves the organization or their permissions change.
sso-ug-058	sso-ug.pdf	58	AWS IAM Identity Center User Guide 5. In the Conﬁgure session settings dialog box, select the checkbox for Enable extended sessions for Amazon Q Developer. Deselect the checkbox to disable extended session duration. 6. Choose Save to return to the Settings page. Delete active user sessions for the AWS access portal and AWS integrated applications IAM Identity Center administrators can delete active user sessions. Deleting user sessions enables administrators to revoke access and remove stale sessions when users no longer require or shouldn’t maintain their current authentication state, such as when an employee leaves the organization or their permissions change. Use the following procedure to view and delete active sessions for an IAM Identity Center user. Note Deleting an active session for an IAM Identity Center user doesn't delete any active IAM Role sessions in the AWS Management Console or AWS CLI. To delete an active session of the AWS access portal and IAM Identity Center integrated applications 1. Open the IAM Identity Center console. 2. Choose Users. 3. On the Users page, choose the username of the user whose sessions you want to manage. This takes you to a page with the user’s information. 4. On the user’s page, choose the Active sessions tab. The number in parentheses next to Active sessions indicates the number of current active sessions for this user. 5. Select the check boxes beside the sessions that you want to delete, and then choose Delete session. A dialog box appears that conﬁrms you're deleting active sessions for this user. Read the information in the dialog box, and if you want to continue, choose Delete session. 6. You are returned to the user's page. A green ﬂash bar appears to indicate that the selected sessions were successfully deleted. Manage sign-in and attribute use for all identity source types 132 AWS IAM Identity Center User Guide For more information on the behavior of revoked authentication sessions, see Authentication sessions. Manage identities in IAM Identity Center IAM Identity Center provides the following capabilities for your users and groups: • Create your users and groups. • Add your users as members to the groups. • Assign the groups with the desired level of access to your AWS accounts and applications. To manage users and groups in the IAM Identity Center store, AWS supports the API operations listed in Identity Center Actions. Provisioning when users are in IAM Identity Center When you create users and groups directly in IAM Identity Center, provisioning is automatic. These identities are immediately available for use in making assignments and for use by applications. For more information, see User and group provisioning. Changing your identity source If you prefer to manage users in AWS Managed Microsoft AD, you can stop using your Identity Center directory at any time and instead connect IAM Identity Center to your directory in Microsoft AD by using AWS Directory Service. For more information, see considerations for Changing between IAM Identity Center directory and Active Directory. If you prefer to manage users in an external identity provider (IdP), you can connect IAM Identity Center to your IdP and enable automatic provisioning. For more information, see considerations for Changing from IAM Identity Center to an external IdP. Topics • Add users to your Identity Center directory • Add groups to your Identity Center directory • Add users to groups • Delete groups in IAM Identity Center • Delete users in IAM Identity Center • Remove users from groups Manage identities in IAM Identity Center 133 AWS IAM Identity Center User Guide • Disable user access to AWS accounts and applications in IAM Identity Center • Edit Identity Center directory user properties • Reset the IAM Identity Center user password for an end user • Email one-time password to users created with API or CLI • Password requirements when managing identities in IAM Identity Center Add users to your Identity Center directory Users and groups that you create in your Identity Center directory are available in IAM Identity Center only. Use the following procedure to add users to your Identity Center directory. Alternatively, you can call the AWS API operation CreateUser to add users. Console To add a user 1. Open the IAM Identity Center console. 2. Choose Users. 3. Choose Add user and provide the following required information: a. Username – This user name is required to sign in to the AWS access portal and can't be changed later. It must be between 1 and 100 characters. b. Password – You can either send an email with the password setup instructions (this is the default option) or generate a one-time password. If you are creating an administrative user and you choose to send an email, make sure that you specify an email address that you can access. i. Send an email to
sso-ug-059	sso-ug.pdf	59	Identity Center console. 2. Choose Users. 3. Choose Add user and provide the following required information: a. Username – This user name is required to sign in to the AWS access portal and can't be changed later. It must be between 1 and 100 characters. b. Password – You can either send an email with the password setup instructions (this is the default option) or generate a one-time password. If you are creating an administrative user and you choose to send an email, make sure that you specify an email address that you can access. i. Send an email to this user with password setup instructions – This option automatically sends the user an email addressed from Amazon Web Services, with the subject line Invitation to join AWS IAM Identity Center. The email invites the user on behalf of your company to access the IAM Identity Center AWS access portal, and registers a password. The email invitation will expire in seven days. If this happens, you can resend the email by choosing Reset password, and then choosing Send an email to the user with instructions for resetting the password. Before the user accepts the invitation, you will see Send email veriﬁcation link, which is meant to verify their email address. However, this step is optional and will disappear after the user accepts the invitation and registers a password. Manage identities in IAM Identity Center 134 AWS IAM Identity Center User Guide Note In certain Regions, IAM Identity Center sends emails to users using Amazon Simple Email Service from another AWS Region. For information about how emails are sent, see Cross-Region emails with Amazon SES. All emails sent by the IAM Identity Center service will come from either the address [email protected] or no- [email protected]. We recommend that you conﬁgure your email system so that it accepts emails from these sender email addresses and does not handle them as junk or spam. ii. Generate a one-time password that you can share with this user – This option provides you with the AWS access portal URL and password details that you can manually send to the user from your email address. The user will need to verify their email address. You can initiate the process by choosing Send email veriﬁcation link. The email veriﬁcation link will expire in seven days. If this happens, you can resend the email veriﬁcation link by choosing Reset password, and then choosing Generate a one-time password and share the password with the user. c. Email address – The email address must be unique. d. Conﬁrm email address e. First name – You must enter a name here for automatic provisioning to work. For more information, see Provisioning an external identity provider into IAM Identity Center using SCIM. f. Last name – You must enter a name here for automatic provisioning to work. g. Display name Note (Optional) If applicable, you can specify values for additional attributes such as the user's Microsoft 365 immutable ID to help provide the user with single sign-on access to certain business applications. 4. Choose Next. Manage identities in IAM Identity Center 135 AWS IAM Identity Center User Guide 5. If applicable, select one or more groups to which you want to add the user, and choose Next. 6. Review the information that you speciﬁed for Step 1: Specify user details and Step 2: Add user to groups - optional. Choose Edit by either step to make any changes. After you conﬁrm that the correct information is speciﬁed for both steps, choose Add user. AWS CLI To add a user The following create-user command creates a new user in your Identity Center directory. aws identitystore create-user \ --identity-store-id d-1234567890 \ --user-name johndoe \ --name "GivenName=John,FamilyName=Doe" \ --display-name "John Doe" \ --emails "Type=work,[email protected]" Output: { "UserId": "1234567890-abcdef", "IdentityStoreId": "d-1234567890" } Note When you create users with the create-user CLI command or the CreateUser API operation, the users don't have passwords. You can update the settings in IAM Identity Center to send these users a veriﬁcation email after their ﬁrst attempt to sign on so they can set up a password. If you don't enable this setting, you must generate a one- time password and share it with the user. For more information, see Email one-time password to users created with API or CLI. Manage identities in IAM Identity Center 136 AWS IAM Identity Center User Guide Add groups to your Identity Center directory Use the following procedure to add groups to your Identity Center directory. Alternatively, you can call the AWS API operation CreateGroup to add groups. Console To add a group 1. Open the IAM Identity Center console. 2. Choose Groups. 3. Choose Create group. 4. Enter a Group name and Description - optional. The description should provide details on what permissions have been
sso-ug-060	sso-ug.pdf	60	it with the user. For more information, see Email one-time password to users created with API or CLI. Manage identities in IAM Identity Center 136 AWS IAM Identity Center User Guide Add groups to your Identity Center directory Use the following procedure to add groups to your Identity Center directory. Alternatively, you can call the AWS API operation CreateGroup to add groups. Console To add a group 1. Open the IAM Identity Center console. 2. Choose Groups. 3. Choose Create group. 4. Enter a Group name and Description - optional. The description should provide details on what permissions have been or will be assigned to the group. Under Add users to group - optional, locate the users you want to add as members. Then select the check box next to each of them. 5. Choose Create group. AWS CLI To add a group The following create-group command creates a new group in your Identity Center directory. aws identitystore create-group \ --identity-store-id d-1234567890 \ --display-name "Developers" \ --description "Group that contains all developers" Output: { "GroupId": "1a2b3c4d-5e6f-7g8h-9i0j-1k2l3m4n5o6p", "IdentityStoreId": "d-1234567890" } After you add this group to your Identity Center directory, you can assign single sign-on access to the group. For more information, see Assign user or group access to AWS accounts. Manage identities in IAM Identity Center 137 AWS IAM Identity Center Add users to groups User Guide Use the following procedure to add users as members of a group that you previously created in your Identity Center directory. Alternatively, you can call the AWS API operation CreateGroupMembership to add a user as a member of a group. Console To add a user as a member of a group 1. Open the IAM Identity Center console. 2. Choose Groups. 3. Choose the group name that you want to update. 4. On the group details page, under Users in this group, choose Add users to group. 5. On the Add users to group page, under Other users, locate the users you want to add as members. Then, select the check box next to each of them. 6. Choose Add users. AWS CLI To add a user as a member of a group The following create-group-membership command adds a user to a group in your Identity Center directory. aws identitystore create-group-membership \ --identity-store-id d-1234567890 \ --group-id a1b2c3d4-5678-90ab-cdef-EXAMPLE22222 \ --member-id UserId=a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 Output: { "MembershipId": "a1b2c3d4-5678-90ab-cdef-EXAMPLE33333", "IdentityStoreId": "d-1234567890" } Manage identities in IAM Identity Center 138 AWS IAM Identity Center User Guide Delete groups in IAM Identity Center When you delete a group in your IAM Identity Center directory, it removes access to AWS accounts and applications for all users who are members of this group. After a group is deleted it cannot be undone. Use the following procedure to delete a group in your Identity Center directory. Important The instructions on this page apply to AWS IAM Identity Center. They do not apply to AWS Identity and Access Management (IAM). IAM Identity Center users, groups, and user credentials are diﬀerent from IAM users, groups, and IAM user credentials. If you are looking for instructions on deleting groups in IAM, see Deleting an IAM user group in the AWS Identity and Access Management User Guide. Console To delete a group 1. Open the IAM Identity Center console. 2. Choose Groups. 3. There are two ways you can delete a group: • On the Groups page, you can select multiple groups for deletion. Select the group name that you want to delete and choose Delete group. • Choose the group name that you want to delete. On the group details page, choose Delete group . 4. You might be asked to conﬁrm your intent to delete the group. • If you delete multiple groups at once, conﬁrm your intent by typing Delete in the Delete group dialog box. • If you delete a single group that contains users, conﬁrm your intent by typing the name of the group you want to delete in the Delete group dialog box. 5. Choose Delete group. If you selected multiple groups for deletion, choose Delete # groups. AWS CLI To delete a group Manage identities in IAM Identity Center 139 AWS IAM Identity Center User Guide The following delete-group command deletes the speciﬁed group from your Identity Center directory. aws identitystore delete-group \ --identity-store-id d-1234567890 \ --group-id a1b2c3d4-5678-90ab-cdef-EXAMPLE22222 Delete users in IAM Identity Center When you delete a user in your IAM Identity Center directory, it removes their access to AWS accounts and applications. After you delete a user, you cannot undo this action. Use the following procedure to delete a user in your Identity Center directory. Note When you disable user access or delete a user in IAM Identity Center, that user will immediately be prevented from signing in to the AWS access portal and will not be able
sso-ug-061	sso-ug.pdf	61	deletes the speciﬁed group from your Identity Center directory. aws identitystore delete-group \ --identity-store-id d-1234567890 \ --group-id a1b2c3d4-5678-90ab-cdef-EXAMPLE22222 Delete users in IAM Identity Center When you delete a user in your IAM Identity Center directory, it removes their access to AWS accounts and applications. After you delete a user, you cannot undo this action. Use the following procedure to delete a user in your Identity Center directory. Note When you disable user access or delete a user in IAM Identity Center, that user will immediately be prevented from signing in to the AWS access portal and will not be able to create new sign in sessions. For more information, see Authentication sessions. Important The instructions on this page apply to AWS IAM Identity Center. They do not apply to AWS Identity and Access Management (IAM). IAM Identity Center users, groups, and user credentials are diﬀerent from IAM users, groups, and IAM user credentials. If you are looking for instructions on deleting users in IAM, see Deleting an IAM user in the AWS Identity and Access Management User Guide. Console To delete a user 1. Open the IAM Identity Center console. 2. Choose Users. 3. There are two ways you can delete a user: Manage identities in IAM Identity Center 140 AWS IAM Identity Center User Guide • On the Users page, you can select multiple users for deletion. Select the username that you want to delete and choose Delete users. • Choose the username that you want to delete. On the user details page, choose Delete user. 4. If you delete multiple users at once, conﬁrm your intent by typing Delete in the Delete user dialog box. 5. Choose Delete user. If you selected multiple users for deletion, choose Delete # users. AWS CLI To delete a user The following delete-user command deletes a user from your Identity Center directory. aws identitystore delete-user \ --identity-store-id d-1234567890 \ --user-id a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 Remove users from groups Use the following procedure to remove members from a group. Alternatively, you can call the AWS API operation DeleteGroupMembership to remove a user from a group. Console To remove a user from a group 1. Open the IAM Identity Center console. 2. Choose Groups. 3. Choose the group you want to update. 4. On the group details page, under the Users in this group, choose the users to remove. 5. Choose Remove users from group. 6. On the Remove users dialog box, choose Remove users from group to verify you want to remove the users access to the account and applications that are assigned to the group. Manage identities in IAM Identity Center 141 AWS IAM Identity Center AWS CLI To remove a user from a group User Guide The following delete-group-membership command removes a membership from a group. aws identitystore delete-group-membership --identity-store-id d-1234567890 \ --membership-id a1b2c3d4-5678-90ab-cdef-EXAMPLE33333 Disable user access to AWS accounts and applications in IAM Identity Center When you disable user access in your IAM Identity Center directory, you can't edit their user details, reset their password, add the user to a group, or view their group membership. Disabling user access prevents them from signing in to the AWS access portal and they will no longer have access to their assigned AWS accounts and applications. Use the following procedure to disable user access in your Identity Center directory using the IAM Identity Center console. Note When you disable user access or delete a user in IAM Identity Center, that user will immediately be prevented from signing in to the AWS access portal and won't be able to create new sign in sessions. For more information, see Authentication sessions. To disable user access in IAM Identity Center 1. Open the IAM Identity Center console. Important The instructions on this page apply to AWS IAM Identity Center. They don't apply to AWS Identity and Access Management (IAM). IAM Identity Center users, groups, and user credentials are diﬀerent from IAM users, groups, and IAM user credentials. If you are looking for instructions on deactivating users in IAM, see Managing IAM users in the AWS Identity and Access Management User Guide. Manage identities in IAM Identity Center 142 AWS IAM Identity Center 2. Choose Users. User Guide 3. Select the username of the user whose access you want to disable. 4. Below the username of the user whose access you want to disable, in the General information section, choose Disable user access. 5. In the Disable user access dialog box, choose Disable user access. Edit Identity Center directory user properties Use the following procedure to edit the properties of a user in your Identity Center directory. Alternatively, you can call the AWS API operation UpdateUser to update user properties. Console To edit user properties in IAM Identity Center 1. Open the IAM Identity Center console. 2. Choose Users. 3.
sso-ug-062	sso-ug.pdf	62	the username of the user whose access you want to disable. 4. Below the username of the user whose access you want to disable, in the General information section, choose Disable user access. 5. In the Disable user access dialog box, choose Disable user access. Edit Identity Center directory user properties Use the following procedure to edit the properties of a user in your Identity Center directory. Alternatively, you can call the AWS API operation UpdateUser to update user properties. Console To edit user properties in IAM Identity Center 1. Open the IAM Identity Center console. 2. Choose Users. 3. Choose the user that you want to edit. 4. On the user Proﬁle page, next to Proﬁle details, choose Edit. 5. On the Edit proﬁle details page, update the properties as needed. Then, choose Save changes . Note (Optional) You can modify additional attributes such as Employee number and Oﬃce 365 Immutable ID to help map the user's identity in IAM Identity Center with certain business applications that users need to use. Note The Email address attribute is an editable ﬁeld and the value you provide must be unique. Manage identities in IAM Identity Center 143 AWS IAM Identity Center AWS CLI User Guide To edit user properties in IAM Identity Center The following update-user command updates the user's nickname. aws identitystore update-user \ --identity-store-id d-1234567890 \ --user-id a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 \ --operations '{"AttributePath":"nickName","AttributeValue":"Johnny"}' Reset the IAM Identity Center user password for an end user This procedure is for administrators who need to reset the password for a user in the IAM Identity Center directory. You'll use the IAM Identity Center console to reset passwords. Considerations for identity providers and user types • Microsoft Active Directory or external provider – If you're connecting IAM Identity Center to Microsoft Active Directory or an external provider, user password resets must be done from within Active Directory or the external provider. This means that passwords for those users can't be reset from the IAM Identity Center console. • Users in the IAM Identity Center directory – If you're an IAM Identity Center user, you can reset your own IAM Identity Center password, see Resetting your AWS access portal user password. To reset a password for an IAM Identity Center end user Important The instructions on this page apply to AWS IAM Identity Center. They do not apply to AWS Identity and Access Management (IAM). IAM Identity Center users, groups, and user credentials are diﬀerent from IAM users, groups, and IAM user credentials. If you are looking for instructions on changing passwords for IAM users, see Managing passwords for IAM users in the AWS Identity and Access Management User Guide. 1. Open the IAM Identity Center console. 2. Choose Users. Manage identities in IAM Identity Center 144 AWS IAM Identity Center User Guide 3. Select the username of the user whose password you want to reset. 4. On the user details page, choose Reset password. 5. In the Reset password dialog box, select one of the following choices, and then choose Reset password: a. Send an email to the user with instructions to reset the password – This option automatically sends the user an email addressed from Amazon Web Services that walks them through how to reset their password. Warning As a security best practice, verify that the email address for this user is correct prior to selecting this option. If this password reset email were to be sent to an incorrect or misconﬁgured email address, a malicious recipient could use it to gain unauthorized access to your AWS environment. b. Generate a one-time password and share the password with the user – This option provides you with the password details that you can manually send to the user from your email address. Email one-time password to users created with API or CLI When you create users with the CreateUser API operation or the create-user CLI command, the users don't have passwords. You can update the settings in IAM Identity Center to send these users a veriﬁcation email after their ﬁrst attempt to sign in, if you’ve speciﬁed an email for the user when they were created. After receiving the veriﬁcation email, the user must set a password to sign in. If you don’t enable this setting, you must generate a one-time password and share it with users that you create using the CreateUser API or create-user CLI command. To send an email address veriﬁcation email to users created with the CreateUser API or create-user CLI command 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Standard authentication section, choose Conﬁgure. Manage identities in IAM Identity Center 145 AWS IAM Identity Center User Guide 5. In the Conﬁgure standard authentication dialog box, select
sso-ug-063	sso-ug.pdf	63	a password to sign in. If you don’t enable this setting, you must generate a one-time password and share it with users that you create using the CreateUser API or create-user CLI command. To send an email address veriﬁcation email to users created with the CreateUser API or create-user CLI command 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Standard authentication section, choose Conﬁgure. Manage identities in IAM Identity Center 145 AWS IAM Identity Center User Guide 5. In the Conﬁgure standard authentication dialog box, select the Send email OTP check box. Then, choose Save. The status updates from Disabled to Enabled. Password requirements when managing identities in IAM Identity Center Note These requirements apply only to users created in the Identity Center directory. If you have conﬁgured an identity source other than IAM Identity Center for authentication, such as Active Directory or an external identity provider, the password policies for your users are deﬁned and enforced in those systems, not in IAM Identity Center. If your identity source is AWS Managed Microsoft AD, see Manage password policies for AWS Managed Microsoft AD for more information. When you use IAM Identity Center as your identity source, users must adhere to the following password requirements to set or change their password: • Passwords are case-sensitive. • Passwords must be between 8 and 64 characters in length. • Passwords must contain at least one character from each of the following four categories: • Lowercase letters (a-z) • Uppercase letters (A-Z) • Numbers (0-9) • Non-alphanumeric characters (~!@#$%^&*_-+=`\|\(){}[]:;"'<>,.?/) • The last three passwords cannot be reused. • Passwords that are publicly known through a data set leaked from a third party cannot be used. Connect to a Microsoft AD directory With AWS IAM Identity Center, you can connect a self-managed directory in Active Directory (AD) or a directory in AWS Managed Microsoft AD by using AWS Directory Service. This Microsoft AD directory deﬁnes the pool of identities that administrators can pull from when using the IAM Identity Center console to assign single sign-on access. After connecting your corporate directory Connect to a Microsoft AD directory 146 AWS IAM Identity Center User Guide to IAM Identity Center, you can then grant your AD users or groups access to AWS accounts, applications, or both. AWS Directory Service helps you to set up and run a standalone AWS Managed Microsoft AD directory hosted in the AWS Cloud. You can also use AWS Directory Service to connect your AWS resources with an existing self-managed AD. To conﬁgure AWS Directory Service to work with your self-managed AD, you must ﬁrst set up trust relationships to extend authentication to the cloud. IAM Identity Center uses the connection provided by AWS Directory Service to perform pass- through authentication to the source AD instance. When you use AWS Managed Microsoft AD as your identity source, IAM Identity Center can work with users from AWS Managed Microsoft AD or from any domain connected through an AD trust. If you want to locate your users in four or more domains, users must use the DOMAIN\user syntax as their user name when performing sign-ins to IAM Identity Center. Notes • As a prerequisite step, make sure your AD Connector or directory in AWS Managed Microsoft AD in AWS Directory Service resides within your AWS Organizations management account. • IAM Identity Center does not support SAMBA 4-based Simple AD as a connected directory. For a demonstration on the process of using Active Directory as an identity source for IAM Identity Center, see the following YouTube video: Using Active Directory as an identity source for AWS IAM Identity Center \| Amazon Web Services Considerations for using Active Directory If you want to use Active Directory as your identity source, your conﬁguration must meet the following prerequisites: • If you're using AWS Managed Microsoft AD, you must enable IAM Identity Center in the same AWS Region where your AWS Managed Microsoft AD directory is set up. IAM Identity Center stores the assignment data in the same Region as the directory. To administer IAM Identity Center, you might need to switch to the Region where IAM Identity Center is conﬁgured. Also, note that the AWS access portal uses the same access URL as your directory. Connect to a Microsoft AD directory 147 AWS IAM Identity Center User Guide • Use an Active Directory residing in the management account: You must have an existing AD Connector or AWS Managed Microsoft AD directory set up in AWS Directory Service, and it must reside within your AWS Organizations management account. You can connect only one AD Connector directory or one directory in AWS Managed Microsoft AD at a time. If you need to support multiple domains or
sso-ug-064	sso-ug.pdf	64	where IAM Identity Center is conﬁgured. Also, note that the AWS access portal uses the same access URL as your directory. Connect to a Microsoft AD directory 147 AWS IAM Identity Center User Guide • Use an Active Directory residing in the management account: You must have an existing AD Connector or AWS Managed Microsoft AD directory set up in AWS Directory Service, and it must reside within your AWS Organizations management account. You can connect only one AD Connector directory or one directory in AWS Managed Microsoft AD at a time. If you need to support multiple domains or forests, use AWS Managed Microsoft AD. For more information, see: • Connect a directory in AWS Managed Microsoft AD to IAM Identity Center • Connect a self-managed directory in Active Directory to IAM Identity Center • Use an Active Directory residing in the delegated admin account: If you plan to enable IAM Identity Center delegated admin and use Active Directory as your IAM Identity Center identity source, you can use an existing AD Connector or AWS Managed Microsoft AD directory set up in AWS Directory residing in the delegated admin account. If you decide to change IAM Identity Center identity source from any other source to Active Directory, or change it from Active Directory to any other source, the directory must reside in (be owned by) the IAM Identity Center delegated administrator member account if one exists; otherwise, it must be in the management account. Connect Active Directory and specify a user If you're already using Active Directory, the following topics will help you prepare to connect your directory to IAM Identity Center. You can connect an AWS Managed Microsoft AD directory or a self-managed directory in Active Directory with IAM Identity Center. Note IAM Identity Center doesn't support SAMBA4-based Simple AD as an identity source. AWS Managed Microsoft AD 1. Review the guidance in Connect to a Microsoft AD directory. 2. Follow the steps in Connect a directory in AWS Managed Microsoft AD to IAM Identity Center. Connect to a Microsoft AD directory 148 AWS IAM Identity Center User Guide 3. Conﬁgure Active Directory to synchronize the user to whom you want to grant administrative permissions into IAM Identity Center. For more information, see Synchronize an administrative user into IAM Identity Center. Self-managed directory in Active Directory 1. Review the guidance in Connect to a Microsoft AD directory. 2. Follow the steps in Connect a self-managed directory in Active Directory to IAM Identity Center. 3. Conﬁgure Active Directory to synchronize the user to whom you want to grant administrative permissions into IAM Identity Center. For more information, see Synchronize an administrative user into IAM Identity Center. External IdP 1. Review the guidance in Manage an external identity provider. 2. Follow the steps in How to connect to an external identity provider. 3. Conﬁgure your IdP to provision users into IAM Identity Center. Note Before you set up automatic, group-based provisioning of all your workforce identities from your IdP into IAM Identity Center, we recommend that you sync the one user to whom you want to grant administrative permissions into IAM Identity Center. Synchronize an administrative user into IAM Identity Center After you connect your Active Directory to IAM Identity Center, you can specify a user to whom you want to grant administrative permissions, and then synchronize that user from your directory into IAM Identity Center. 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. On the Manage Sync page, choose the Users tab, and then choose Add users and groups. Connect to a Microsoft AD directory 149 AWS IAM Identity Center User Guide 5. On the Users tab, under User, enter the exact user name and choose Add. 6. Under Added Users and Groups, do the following: a. b. c. Conﬁrm that the user to whom you want to grant administrative permissions is speciﬁed. Select the check box to the left of the user name. Choose Submit. 7. 8. In the Manage sync page, the user that you speciﬁed appears in the Users in sync scope list. In the navigation pane, choose Users. 9. On the Users page, it might take some time for the user that you speciﬁed to appear in the list. Choose the refresh icon to update the list of users. At this point, your user doesn't have access to the management account. You will set up administrative access to this account by creating an administrative permission set and assigning the user to that permission set. For more information, see Create a permission set. Provisioning when users come from Active Directory IAM Identity Center uses the connection provided by the AWS Directory Service to synchronize user, group,
sso-ug-065	sso-ug.pdf	65	pane, choose Users. 9. On the Users page, it might take some time for the user that you speciﬁed to appear in the list. Choose the refresh icon to update the list of users. At this point, your user doesn't have access to the management account. You will set up administrative access to this account by creating an administrative permission set and assigning the user to that permission set. For more information, see Create a permission set. Provisioning when users come from Active Directory IAM Identity Center uses the connection provided by the AWS Directory Service to synchronize user, group, and membership information from your source directory in Active Directory to the IAM Identity Center identity store. No password information is synchronized to IAM Identity Center, because user authentication takes place directly from the source directory in Active Directory. This identity data is used by applications to facilitate in-app lookup, authorization, and collaboration scenarios without passing LDAP activity back to the source directory in Active Directory. For more information above provisioning, see User and group provisioning. Topics • Connect a directory in AWS Managed Microsoft AD to IAM Identity Center • Connect a self-managed directory in Active Directory to IAM Identity Center • Attribute mappings between IAM Identity Center and External Identity Providers directory • IAM Identity Center conﬁgurable AD sync Connect a directory in AWS Managed Microsoft AD to IAM Identity Center Use the following procedure to connect a directory in AWS Managed Microsoft AD that is managed by AWS Directory Service to IAM Identity Center. Connect to a Microsoft AD directory 150 AWS IAM Identity Center User Guide To connect AWS Managed Microsoft AD to IAM Identity Center 1. Open the IAM Identity Center console. Note Make sure that the IAM Identity Center console is using one of the Regions where your AWS Managed Microsoft AD directory is located before you move to the next step. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, and then choose Actions > Change identity source. 4. Under Choose identity source, select Active Directory, and then choose Next. 5. Under Connect active directory, choose a directory in AWS Managed Microsoft AD from the list, and then choose Next. 6. Under Conﬁrm change, review the information and when ready type ACCEPT, and then choose Change identity source. Important To specify a user in Active Directory as an administrative user in IAM Identity Center, you must ﬁrst synchronize the user to whom you want to grant administrative permissions from Active Directory into IAM Identity Center. To do so, follow the steps in Synchronize an administrative user into IAM Identity Center. Connect a self-managed directory in Active Directory to IAM Identity Center Users in your self-managed directory in Active Directory (AD) can also have single sign-on access to AWS accounts and applications in the AWS access portal. To conﬁgure single sign-on access for these users, you can do either of the following: • Create a two-way trust relationship – When two-way trust relationships are created between AWS Managed Microsoft AD and a self-managed directory in AD, users in your self-managed directory in AD can sign in with their corporate credentials to various AWS services and business applications. One-way trusts do not work with IAM Identity Center. Connect to a Microsoft AD directory 151 AWS IAM Identity Center User Guide AWS IAM Identity Center requires a two-way trust so that it has permissions to read user and group information from your domain to synchronize user and group metadata. IAM Identity Center uses this metadata when assigning access to permission sets or applications. User and group metadata is also used by applications for collaboration, like when you share a dashboard with another user or group. The trust from AWS Directory Service for Microsoft Active Directory to your domain permits IAM Identity Center to trust your domain for authentication. The trust in the opposite direction grants AWS permissions to read user and group metadata. For more information about setting up a two-way trust, see When to Create a Trust Relationship in the AWS Directory Service Administration Guide. Note In order to use AWS applications, like IAM Identity Center to read AWS Directory Service directory users from trusted domains, the AWS Directory Service accounts require permissions to the userAccountControl attribute on the trusted users. Without read permissions to this attribute, AWS applications are unable to determine if the account is enabled or disabled. Read access to this attribute is provided by default when a trust is created. If you deny access to this attribute (not recommended), you will break applications like Identity Center from being able to read trusted users. The solution is to speciﬁcally allow Read access to the userAccountControl attribute on the AWS service accounts under the AWS Reserved OU (preﬁxed with
sso-ug-066	sso-ug.pdf	66	directory users from trusted domains, the AWS Directory Service accounts require permissions to the userAccountControl attribute on the trusted users. Without read permissions to this attribute, AWS applications are unable to determine if the account is enabled or disabled. Read access to this attribute is provided by default when a trust is created. If you deny access to this attribute (not recommended), you will break applications like Identity Center from being able to read trusted users. The solution is to speciﬁcally allow Read access to the userAccountControl attribute on the AWS service accounts under the AWS Reserved OU (preﬁxed with AWS_). • Create an AD Connector – AD Connector is a directory gateway that can redirect directory requests to your self-managed AD without caching any information in the cloud. For more information, see Connect to a Directory in the AWS Directory Service Administration Guide. The following are considerations when using AD Connector: • If you are connecting IAM Identity Center to an AD Connector directory, any future user password resets must be done from within AD. This means that users won't be able to reset their passwords from the AWS access portal. • If you use AD Connector to connect your Active Directory Domain Service to IAM Identity Center, IAM Identity Center only has access to the users and groups of the single domain to which AD Connector attaches. If you need to support multiple domains or forests, use AWS Directory Service for Microsoft Active Directory. Connect to a Microsoft AD directory 152 AWS IAM Identity Center Note User Guide IAM Identity Center does not work with SAMBA4-based Simple AD directories. Attribute mappings between IAM Identity Center and External Identity Providers directory Attribute mappings are used to map attribute types that exist in IAM Identity Center with like attributes in your external identity source such as Google Workspace, Microsoft Active Directory (AD), and Okta. IAM Identity Center retrieves user attributes from your identity source and maps them to IAM Identity Center user attributes. If your IAM Identity Center is synchronized to use an external identity provider (IdP), like Google Workspace, Okta, or Ping as the identity source, you'll need to map your attributes in your IdP. IAM Identity Center preﬁlls a set of attributes for you under the Attribute mappings tab found on its conﬁguration page. IAM Identity Center uses these user attributes to populate SAML assertions (as SAML attributes) that are sent to the application. These user attributes are in turn retrieved from your identity source. Each application determines the list of SAML 2.0 attributes it needs for successful single sign-on. For more information, see Map attributes in your application to IAM Identity Center attributes. IAM Identity Center also manages a set of attributes for you under the Attribute mappings section of your Active Directory conﬁguration page if you're using Active Directory as an identity source. For more information, see Mapping user attributes between IAM Identity Center and Microsoft AD directory. Supported external identity provider attributes The following table lists all external identity provider (IdP) attributes supported and can be mapped to attributes you can use when conﬁguring Attributes for access control in IAM Identity Center. When using SAML assertions, you can use whichever attributes your IdP supports. Supported attributes in your IdP ${path:userName} Connect to a Microsoft AD directory 153 AWS IAM Identity Center User Guide Supported attributes in your IdP ${path:name.familyName} ${path:name.givenName} ${path:displayName} ${path:nickName} ${path:emails[primary eq true].value} ${path:addresses[type eq "work"].streetAddress} ${path:addresses[type eq "work"].locality} ${path:addresses[type eq "work"].region} ${path:addresses[type eq "work"].postalCode} ${path:addresses[type eq "work"].country} ${path:addresses[type eq "work"].formatted} ${path:phoneNumbers[type eq "work"].value} ${path:userType} ${path:title} ${path:locale} ${path:timezone} ${path:enterprise.employeeNumber} ${path:enterprise.costCenter} ${path:enterprise.organization} ${path:enterprise.division} Connect to a Microsoft AD directory 154 AWS IAM Identity Center User Guide Supported attributes in your IdP ${path:enterprise.department} ${path:enterprise.manager.value} Default mappings between IAM Identity Center and Microsoft AD The following table lists the default mappings for user attributes in IAM Identity Center to the user attributes in your Microsoft AD directory. IAM Identity Center only supports the list of attributes in the User attribute in IAM Identity Center column. User attribute in IAM Identity Center Maps to this attribute in your Active Directory displayname ${displayname} emails[?primary].value * ${mail} externalid name.givenname ${objectguid} ${givenname} name.familyname ${sn} name.middlename ${initials} username ${userprincipalname} * The email attribute in IAM Identity Center must be unique within the directory. Group attribute in IAM Identity Center Maps to this attribute in your Active Directory externalid description ${objectguid} ${description} Connect to a Microsoft AD directory 155 AWS IAM Identity Center User Guide Group attribute in IAM Identity Center Maps to this attribute in your Active Directory displayname ${samaccountname}@{associat eddomain} Considerations • If you don't have any assignments for your users and groups in IAM Identity Center when you enable conﬁgurable AD sync, the default mappings in the previous tables are used. For information about how to customize these mappings,
sso-ug-067	sso-ug.pdf	67	email attribute in IAM Identity Center must be unique within the directory. Group attribute in IAM Identity Center Maps to this attribute in your Active Directory externalid description ${objectguid} ${description} Connect to a Microsoft AD directory 155 AWS IAM Identity Center User Guide Group attribute in IAM Identity Center Maps to this attribute in your Active Directory displayname ${samaccountname}@{associat eddomain} Considerations • If you don't have any assignments for your users and groups in IAM Identity Center when you enable conﬁgurable AD sync, the default mappings in the previous tables are used. For information about how to customize these mappings, see Conﬁgure attribute mappings for your sync. • Certain IAM Identity Center attributes can't be modiﬁed because they are immutable and mapped by default to speciﬁc Microsoft AD directory attributes. For example, "username" is a mandatory attribute in IAM Identity Center. If you map "username" to an AD directory attribute with an empty value, IAM Identity Center will consider the windowsUpn value as the default value for "username". If you want to change the attribute mapping for "username" from your current mapping, conﬁrm IAM Identity Center ﬂows with dependency on "username" will continue to work as expected, before making the change. Supported Microsoft AD attributes for IAM Identity Center The following table lists all Microsoft AD directory attributes that are supported and that can be mapped to user attributes in IAM Identity Center. Supported attributes in your Microsoft AD directory ${samaccountname} ${description} ${objectguid} ${givenname} ${sn} Connect to a Microsoft AD directory 156 AWS IAM Identity Center User Guide Supported attributes in your Microsoft AD directory ${initials} ${mail} ${userprincipalname} ${displayname} ${distinguishedname} ${proxyaddresses[?type == "SMTP"].value} ${proxyaddresses[?type == "smpt"].value} ${useraccountcontrol} ${associateddomain} Considerations • You can specify any combination of supported Microsoft AD directory attributes to map to a single mutable attribute in IAM Identity Center. Supported IAM Identity Center attributes for Microsoft AD The following table lists all IAM Identity Center attributes that are supported and that can be mapped to user attributes in your Microsoft AD directory. After you set up your application attribute mappings, you can use these same IAM Identity Center attributes to map to actual attributes used by that application. Supported attributes in IAM Identity Center for Active Directory ${user:AD_GUID} ${user:email} ${user:familyName} Connect to a Microsoft AD directory 157 AWS IAM Identity Center User Guide Supported attributes in IAM Identity Center for Active Directory ${user:givenName} ${user:middleName} ${user:name} ${user:preferredUsername} ${user:subject} Mapping user attributes between IAM Identity Center and Microsoft AD directory You can use the following procedure to specify how your user attributes in IAM Identity Center should map to corresponding attributes in your Microsoft AD directory. To map attributes in IAM Identity Center to attributes in your directory 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Attributes for access control tab, and then choose Manage Attributes. 4. On the Manage attribute for access control page, ﬁnd the attribute in IAM Identity Center that you want to map and then type a value in the text box. For example, you might want to map the IAM Identity Center user attribute email to the Microsoft AD directory attribute ${mail}. 5. Choose Save changes. IAM Identity Center conﬁgurable AD sync IAM Identity Center conﬁgurable Active Directory (AD) sync enables you to explicitly conﬁgure the identities in Microsoft Active Directory that are automatically synchronized into IAM Identity Center and control the synchronization process. • With this sync method, you can do the following: Connect to a Microsoft AD directory 158 AWS IAM Identity Center User Guide • Control data boundaries by explicitly deﬁning the users and groups in Microsoft Active Directory that are automatically synchronized into IAM Identity Center. You can add users and groups or remove users and groups to change the scope of the sync at any time. • Assign synchronized users and groups single sign-on access to AWS accounts or access to applications. The applications can be AWS managed applications or customer managed applications. • Control the synchronization process by pausing and resuming the sync as needed. This helps you regulate the load on production systems. Prerequisites and considerations Before you use conﬁgurable AD sync, be aware of the following prerequisites and considerations: • Specifying users and groups in Active Directory to sync Before you can use IAM Identity Center to assign new users and groups access to AWS accounts and to AWS managed applications or customer managed applications, you must specify the users and groups in Active Directory to sync, and then sync them into IAM Identity Center. • Conﬁgurable AD sync – IAM Identity Center doesn't search your domain controller directly for users and groups. Instead, you must ﬁrst specify the list of users and groups to sync. You can conﬁgure this list, also known as the sync scope,
sso-ug-068	sso-ug.pdf	68	and considerations: • Specifying users and groups in Active Directory to sync Before you can use IAM Identity Center to assign new users and groups access to AWS accounts and to AWS managed applications or customer managed applications, you must specify the users and groups in Active Directory to sync, and then sync them into IAM Identity Center. • Conﬁgurable AD sync – IAM Identity Center doesn't search your domain controller directly for users and groups. Instead, you must ﬁrst specify the list of users and groups to sync. You can conﬁgure this list, also known as the sync scope, in one of the following ways, depending on whether you have users and groups that are already synced into IAM Identity Center, or you have new users and groups that you are syncing for the ﬁrst time by using conﬁgurable AD sync. • Existing users and groups: If you have users and groups that are already synced into IAM Identity Center, the sync scope in conﬁgurable AD sync is prepopulated with a list of those users and groups. To assign new users or groups, you must speciﬁcally add them to the sync scope. For more information, see Add users and groups to your sync scope. • New users and groups: If you want to assign new users and groups access to AWS accounts and to applications, you must specify which users and groups to add to the sync scope in conﬁgurable AD sync before you can use IAM Identity Center to make the assignment. For more information, see Add users and groups to your sync scope. • Making assignments to nested groups in Active Directory Connect to a Microsoft AD directory 159 AWS IAM Identity Center User Guide Groups that are members of other groups are called nested groups (or child groups). • Conﬁgurable AD sync – Using conﬁgurable AD sync to make assignments to a group in Active Directory that contains nested groups might increase the scope of users who have access to AWS accounts or to applications. In this case, the assignment applies to all users, including those in nested groups. For example, if you assign access to Group A, and Group B is a member of Group A, members of Group B also inherit this access. • Updating automated workﬂows If you have automated workﬂows that use the IAM Identity Center identity store API actions and IAM Identity Center assignment API actions to assign new users and groups access to accounts and to applications, and to sync them into IAM Identity Center, you must adjust those workﬂows by April 15, 2022 so that they function as expected with conﬁgurable AD sync. Conﬁgurable AD sync changes the order in which user and group assignment and provisioning occur, and the way in which queries are performed. • Conﬁgurable AD sync – Provisioning occurs ﬁrst, and it is not automatically performed. Instead, you must ﬁrst explicitly add users and groups to the identity store by adding them to your sync scope. For information about the recommended steps for automating your sync conﬁguration for conﬁgurable AD sync, see Automate your sync conﬁguration for conﬁgurable AD sync. Topics • How conﬁgurable AD sync works • First-time Active Directory to IAM Identity Center sync setup • Add users and groups to your sync scope • Remove users and groups from your sync scope • Pause and resume your sync • Conﬁgure attribute mappings for your sync • Automate your sync conﬁguration for conﬁgurable AD sync How conﬁgurable AD sync works IAM Identity Center refreshes the AD-based identity data in the identity store by using the following process. To learn more about the prerequisites, see Prerequisites and considerations. Connect to a Microsoft AD directory 160 AWS IAM Identity Center Creation User Guide After you connect your self-managed directory in Active Directory or your AWS Managed Microsoft AD directory that is managed by AWS Directory Service to IAM Identity Center, you can explicitly conﬁgure the Active Directory users and groups that you want to sync into the IAM Identity Center identity store. The identities that you choose will be synchronized every three hours or so into the IAM Identity Center identity store. Depending on the size of your directory, the sync process might take longer. Groups that are members of other groups (called nested groups or child groups) are also written to the identity store. You can only assign access to new users or groups after they are synchronized into the IAM Identity Center identity store. Update The identity data in the IAM Identity Center identity store stays fresh by periodically reading data from the source directory in Active Directory. IAM Identity Center syncs data from your Active Directory every hour in a sync cycle by default. It may take 30 minutes to 2 hours
sso-ug-069	sso-ug.pdf	69	size of your directory, the sync process might take longer. Groups that are members of other groups (called nested groups or child groups) are also written to the identity store. You can only assign access to new users or groups after they are synchronized into the IAM Identity Center identity store. Update The identity data in the IAM Identity Center identity store stays fresh by periodically reading data from the source directory in Active Directory. IAM Identity Center syncs data from your Active Directory every hour in a sync cycle by default. It may take 30 minutes to 2 hours for the data to sync into IAM Identity Center, based on the size of your Active Directory. User and group objects that are in the sync scope and their memberships are created or updated in IAM Identity Center to map to the corresponding objects in the source directory in Active Directory. For user attributes, only the subset of attributes listed in the Attributes for access control section of the IAM Identity Center console are updated in IAM Identity Center. It may take one sync cycle for any attribute updates you make in Active Directory to reﬂect in IAM Identity Center. You can also update the subset of users and groups that you synchronize into the IAM Identity Center identity store. You can choose to add new users or groups to this subset, or remove them. Any identities that you add are synchronized at the next scheduled sync. Identities that you remove from the subset will stop being updated in the IAM Identity Center identity store. Any user who isn't synchronized for more than 28 days will be disabled in the IAM Identity Center identity store. The corresponding user objects will be automatically disabled in the IAM Identity Center identity store during the next sync cycle, unless they are part of another group that is still part of the sync scope. Deletion Users and groups are deleted from the IAM Identity Center identity store when the corresponding user or group objects are deleted from the source directory in Active Directory. Alternatively, you Connect to a Microsoft AD directory 161 AWS IAM Identity Center User Guide can explicitly delete user objects from the IAM Identity Center identity store by using the IAM Identity Center console. If you use the IAM Identity Center console, you must also remove the users from the sync scope to ensure that they aren't re-synced back into IAM Identity Center during the next sync cycle. You can also pause and restart synchronization at any time. If you pause synchronization for more than 28 days, all your users will be disabled. First-time Active Directory to IAM Identity Center sync setup If you're synchronizing your users and groups from Active Directory into IAM Identity Center for the ﬁrst time, follow these steps. Alternatively, you can follow steps outlined in Change your identity source to change your identity source from IAM Identity Center to Active Directory. Guided setup 1. Open the IAM Identity Center console. Note Make sure that the IAM Identity Center console is using one of the AWS Regions where your AWS Managed Microsoft AD directory is located before you move to the next step. 2. Choose Settings. 3. At the top of the page, in the notiﬁcation message, choose Start guided setup. 4. 5. 6. In Step 1 – optional: Conﬁgure attribute mappings, review the default user and group attribute mappings. If no changes are required, choose Next. If changes are required, make the changes, and then choose Save changes. In Step 2 – optional: Conﬁgure sync scope, choose the Users tab. Then, enter the exact username of the user that you want to add to your sync scope and choose Add. Next, choose the Groups tab. Enter the exact group name of the group that you want to add to your sync scope and choose Add. Then, choose Next. If you want to add users and groups to your sync scope later, make no changes and choose Next. In Step 3: Review and save conﬁguration, conﬁrm your Attribute mappings in Step 1: Attribute mappings and your Users and groups in Step 2: Sync scope. Choose Save conﬁguration. This takes you to the Manage Sync page. Connect to a Microsoft AD directory 162 AWS IAM Identity Center User Guide Add users and groups to your sync scope Add your Active Directory users and groups to IAM Identity Center by following these steps. To add users 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. On the Manage Sync page, choose the Users tab, and then choose Add users and groups. 5. On the Users tab, under User, enter the
sso-ug-070	sso-ug.pdf	70	This takes you to the Manage Sync page. Connect to a Microsoft AD directory 162 AWS IAM Identity Center User Guide Add users and groups to your sync scope Add your Active Directory users and groups to IAM Identity Center by following these steps. To add users 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. On the Manage Sync page, choose the Users tab, and then choose Add users and groups. 5. On the Users tab, under User, enter the exact user name and choose Add. 6. Under Added Users and Groups, review the user that you want to add. 7. Choose Submit. 8. In the navigation pane, choose Users. If the user that you speciﬁed doesn't display in the list, choose the refresh icon to update the list of users. To add groups 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. On the Manage Sync page, choose the Groups tab, and then choose Add users and groups. 5. Choose the Groups tab. Under Group, enter the exact group name and choose Add. 6. Under Added Users and Groups, review the group that you want to add. 7. Choose Submit. 8. In the navigation pane, choose Groups. If the group that you speciﬁed doesn't display in the list, choose the refresh icon to update the list of groups. Remove users and groups from your sync scope For more information about what happens when you remove users and groups from your sync scope, see How conﬁgurable AD sync works. Connect to a Microsoft AD directory 163 AWS IAM Identity Center To remove users 1. Open the IAM Identity Center console. 2. Choose Settings. User Guide 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. Choose the Users tab. 5. Under Users in sync scope, select the check box beside the user that you want to delete. To delete all users, select the check box beside Username. 6. Choose Remove. To remove groups 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. Choose the Groups tab. 5. Under Groups in sync scope, select the check box beside the user that you want to delete. To delete all groups, select the check box beside Group name. 6. Choose Remove. Pause and resume your sync Pausing your sync pauses all future sync cycles and prevents any changes that you make to users and groups in Active Directory from being reﬂected in IAM Identity Center. After you resume the sync, the sync cycle picks up these changes from the next scheduled sync. To pause your sync 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. Under Manage Sync, choose Pause sync. Connect to a Microsoft AD directory 164 AWS IAM Identity Center To resume your sync 1. Open the IAM Identity Center console. 2. Choose Settings. User Guide 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. Under Manage Sync, choose Resume sync. Note If you see Pause sync instead of Resume sync, the sync from Active Directory to IAM Identity Center has already resumed. Conﬁgure attribute mappings for your sync For more information about available attributes, see Attribute mappings between IAM Identity Center and External Identity Providers directory. To conﬁgure attribute mappings in IAM Identity Center to your directory 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, choose Actions, and then choose Manage Sync. 4. Under Manage Sync, choose View attribute mapping. 5. Under Active Directory user attributes, conﬁgure IAM Identity Center identity store attributes and Active Directory user attributes. For example, you might want to map the IAM Identity Center identity store attribute email to the Active Directory user directory attribute ${objectguid}. Note Under Group attributes, IAM Identity Center identity store attributes and Active Directory group attributes can't be changed. 6. Choose Save changes. This returns you to the Manage Sync page. Connect to a Microsoft AD directory 165 AWS IAM Identity Center User Guide Automate your sync conﬁguration for conﬁgurable AD sync To ensure that your automated workﬂow works as expected with conﬁgurable AD sync, we recommend that you perform the following steps to automate your sync conﬁguration. To automate your sync conﬁguration for conﬁgurable AD sync 1. In Active Directory, create a parent
sso-ug-071	sso-ug.pdf	71	the Active Directory user directory attribute ${objectguid}. Note Under Group attributes, IAM Identity Center identity store attributes and Active Directory group attributes can't be changed. 6. Choose Save changes. This returns you to the Manage Sync page. Connect to a Microsoft AD directory 165 AWS IAM Identity Center User Guide Automate your sync conﬁguration for conﬁgurable AD sync To ensure that your automated workﬂow works as expected with conﬁgurable AD sync, we recommend that you perform the following steps to automate your sync conﬁguration. To automate your sync conﬁguration for conﬁgurable AD sync 1. In Active Directory, create a parent sync group to contain all users and groups that you want to sync into IAM Identity Center. For example, you can name the group IAMIdentityCenterAllUsersAndGroups. 2. In IAM Identity Center, add the parent sync group to your conﬁgurable sync list. IAM Identity Center will synchronize all users, groups, sub-groups, and members of all groups contained within the parent sync group. 3. Use the Active Directory user and group management API actions provided by Microsoft to add or remove users and groups from the parent sync group. Manage an external identity provider With IAM Identity Center, you can connect your existing workforce identities from external identity providers (IdPs) through the Security Assertion Markup Language (SAML) 2.0 and System for Cross- Domain Identity Management (SCIM) protocols. This enables your users to sign in to the AWS access portal with their corporate credentials. They can then navigate to their assigned accounts, roles, and applications hosted in external IdPs. For example, you can connect an external IdP such as Okta or Microsoft Entra ID, to IAM Identity Center. Your users can then sign in to the AWS access portal with their existing Okta or Microsoft Entra ID credentials. To control what your users can do once they've signed in, you can assign them access permissions centrally across all the accounts and applications in your AWS organization. In addition, developers can simply sign in to the AWS Command Line Interface (AWS CLI) using their existing credentials, and beneﬁt from automatic short-term credential generation and rotation. If you're using a self-managed directory in Active Directory or an AWS Managed Microsoft AD, see Connect to a Microsoft AD directory. Manage an external identity provider 166 AWS IAM Identity Center Note User Guide The SAML protocol does not provide a way to query the IdP to learn about users and groups. Therefore, you must make IAM Identity Center aware of those users and groups by provisioning them into IAM Identity Center. Provisioning when users come from an external IdP When using an external IdP, you must provision all applicable users and groups into IAM Identity Center before you can make any assignments to AWS accounts or applications. To do this, you can conﬁgure Provisioning an external identity provider into IAM Identity Center using SCIM for your users and groups, or use Manual provisioning. Regardless of how you provision users, IAM Identity Center redirects the AWS Management Console, command line interface, and application authentication to your external IdP. IAM Identity Center then grants access to those resources based on policies you create in IAM Identity Center. For more information about provisioning, see User and group provisioning. Topics • How to connect to an external identity provider • How to change an external identity provider's metadata in IAM Identity Center • Using SAML and SCIM identity federation with external identity providers • SCIM proﬁle and SAML 2.0 implementation How to connect to an external identity provider There are diﬀerent prerequisites, considerations, and provisioning procedures for the supported external IdPs. There are step-by-step tutorials available for several IdPs: • CyberArk • Google Workspace • JumpCloud • Microsoft Entra ID • Okta • OneLogin Manage an external identity provider 167 AWS IAM Identity Center • Ping Identity User Guide For more information on the considerations for external IdPs that IAM Identity Center supports, see Using SAML and SCIM identity federation with external identity providers. The following procedure provides a general overview of the procedure that's used with all external identity providers. To connect to an external identity provider 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab, and then choose Actions > Change identity source. 4. Under Choose identity source, select External identity provider, and then choose Next. 5. Under Conﬁgure external identity provider, do the following: a. Under Service provider metadata, choose Download metadata ﬁle to download the metadata ﬁle and save it on your system. The IAM Identity Center SAML metadata ﬁle is required by your external identity provider. b. Under Identity provider metadata, choose Choose ﬁle, and locate the metadata ﬁle that you downloaded from your external identity provider. Then upload the ﬁle. This metadata ﬁle contains the
sso-ug-072	sso-ug.pdf	72	page, choose the Identity source tab, and then choose Actions > Change identity source. 4. Under Choose identity source, select External identity provider, and then choose Next. 5. Under Conﬁgure external identity provider, do the following: a. Under Service provider metadata, choose Download metadata ﬁle to download the metadata ﬁle and save it on your system. The IAM Identity Center SAML metadata ﬁle is required by your external identity provider. b. Under Identity provider metadata, choose Choose ﬁle, and locate the metadata ﬁle that you downloaded from your external identity provider. Then upload the ﬁle. This metadata ﬁle contains the necessary public x509 certiﬁcate used to trust messages that are sent from the IdP. c. Choose Next. Important Changing your source to or from Active Directory removes all existing user and group assignments. You must manually reapply assignments after you have successfully changed your source. 6. After you read the disclaimer and are ready to proceed, enter ACCEPT. 7. Choose Change identity source. A status message informs you that you successfully changed the identity source. Manage an external identity provider 168 AWS IAM Identity Center User Guide How to change an external identity provider's metadata in IAM Identity Center You can change your external identity provider's metadata which you previously supplied to the IAM Identity Center. These changes aﬀect your users' ability to sign in and access AWS resources through IAM Identity Center. The following procedure describes how to update your external IdP's metadata that's stored in IAM Identity Center. To complete this procedure, you'll need an Organization instance of IAM Identity Center. For more information, see Organization and account instances of IAM Identity Center. To change an external identity provider's metadata 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Identity source tab. Choose Actions and then choose Manage Authentication. 4. In the Identity provider metadata section, choose Edit IdP metadata. You can make the changes to the IdP sign-in URL and or IdP issuer URL for your external IdP on this page. Choose Save changes when you've made all the necessary changes. Using SAML and SCIM identity federation with external identity providers IAM Identity Center implements the following standards-based protocols for identity federation: • SAML 2.0 for user authentication • SCIM for provisioning Any identity provider (IdP) that implements these standard protocols is expected to interoperate successfully with IAM Identity Center, with the following special considerations: • SAML • IAM Identity Center requires a SAML nameID format of email address (that is, urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress). • The value of the nameID ﬁeld in assertions must be an RFC 2822 (https://tools.ietf.org/html/ rfc2822) addr-spec compliant (“[email protected]”) string (https://tools.ietf.org/html/ rfc2822#section-3.4.1). • The metadata ﬁle cannot be over 75000 characters. Manage an external identity provider 169 AWS IAM Identity Center User Guide • The metadata must contain an entityId, X509 certiﬁcate, and SingleSignOnService as part of the sign-in URL. • An encryption key is not supported. • SCIM • The IAM Identity Center SCIM implementation is based on SCIM RFCs 7642 (https:// tools.ietf.org/html/rfc7642), 7643 (https://tools.ietf.org/html/rfc7643), and 7644 (https:// tools.ietf.org/html/rfc7644), and the interoperability requirements laid out in the March 2020 draft of the FastFed Basic SCIM Proﬁle 1.0 (https://openid.net/specs/fastfed- scim-1_0-02.html#rfc.section.4). Any diﬀerences between these documents and the current implementation in IAM Identity Center are described in the Supported API operations section of the IAM Identity Center SCIM Implementation Developer Guide. IdPs that do not conform to the standards and considerations mentioned above are not supported. Please contact your IdP for questions or clariﬁcations regarding the conformance of their products to these standards and considerations. If you have any issues connecting your IdP to IAM Identity Center, we recommend that you check: • AWS CloudTrail logs by ﬁltering on the event name ExternalIdPDirectoryLogin • IdP-speciﬁc logs and/or debug logs • Troubleshooting IAM Identity Center issues Note Some IdPs, such as the ones in the IAM Identity Center identity source tutorials, oﬀer a simpliﬁed conﬁguration experience for IAM Identity Center in the form of an “application” or “connector” built speciﬁcally for IAM Identity Center. If your IdP provides this option, we recommend that you use it, being careful to choose the item that’s built speciﬁcally for IAM Identity Center. Other items called “AWS”, “AWS federation”, or similar generic "AWS" names may use other federation approaches and/or endpoints, and may not work as expected with IAM Identity Center. Manage an external identity provider 170 AWS IAM Identity Center User Guide SCIM proﬁle and SAML 2.0 implementation Both SCIM and SAML are important considerations for conﬁguring IAM Identity Center. SAML 2.0 implementation IAM Identity Center supports identity federation with SAML (Security Assertion Markup Language) 2.0. This allows IAM Identity Center to authenticate identities from external identity providers (IdPs). SAML 2.0 is an open standard used for securely exchanging SAML assertions. SAML
sso-ug-073	sso-ug.pdf	73	Other items called “AWS”, “AWS federation”, or similar generic "AWS" names may use other federation approaches and/or endpoints, and may not work as expected with IAM Identity Center. Manage an external identity provider 170 AWS IAM Identity Center User Guide SCIM proﬁle and SAML 2.0 implementation Both SCIM and SAML are important considerations for conﬁguring IAM Identity Center. SAML 2.0 implementation IAM Identity Center supports identity federation with SAML (Security Assertion Markup Language) 2.0. This allows IAM Identity Center to authenticate identities from external identity providers (IdPs). SAML 2.0 is an open standard used for securely exchanging SAML assertions. SAML 2.0 passes information about a user between a SAML authority (called an identity provider or IdP), and a SAML consumer (called a service provider or SP). The IAM Identity Center service uses this information to provide federated single sign-on. Single sign-on allows users to access AWS accounts and conﬁgured applications based on their existing identity provider credentials. IAM Identity Center adds SAML IdP capabilities to your IAM Identity Center store, AWS Managed Microsoft AD, or to an external identity provider. Users can then single sign-on into services that support SAML, including the AWS Management Console and third-party applications such as Microsoft 365, Concur, and Salesforce. The SAML protocol however doesn't provide a way to query the IdP to learn about users and groups. Therefore, you must make IAM Identity Center aware of those users and groups by provisioning them into IAM Identity Center. SCIM proﬁle IAM Identity Center provides support for the System for Cross-domain Identity Management (SCIM) v2.0 standard. SCIM keeps your IAM Identity Center identities in sync with identities from your IdP. This includes any provisioning, updates, and deprovisioning of users between your IdP and IAM Identity Center. For more information about how to implement SCIM, see Provisioning an external identity provider into IAM Identity Center using SCIM. For additional details about IAM Identity Center’s SCIM implementation, see the IAM Identity Center SCIM Implementation Developer Guide. Topics • Provisioning an external identity provider into IAM Identity Center using SCIM • Rotate SAML 2.0 certiﬁcates Manage an external identity provider 171 AWS IAM Identity Center User Guide Provisioning an external identity provider into IAM Identity Center using SCIM IAM Identity Center supports automatic provisioning (synchronization) of user and group information from your identity provider (IdP) into IAM Identity Center using the System for Cross- domain Identity Management (SCIM) v2.0 protocol. When you conﬁgure SCIM synchronization, you create a mapping of your identity provider (IdP) user attributes to the named attributes in IAM Identity Center. This causes the expected attributes to match between IAM Identity Center and your IdP. You conﬁgure this connection in your IdP using your SCIM endpoint for IAM Identity Center and a bearer token that you create in IAM Identity Center. Topics • Considerations for using automatic provisioning • How to monitor access token expiry • Enable automatic provisioning • Disable automatic provisioning • Generate an access token • Delete an access token • Rotate an access token • Manual provisioning Considerations for using automatic provisioning Before you begin deploying SCIM, we recommend that you ﬁrst review the following important considerations about how it works with IAM Identity Center. For additional provisioning considerations, see the IAM Identity Center identity source tutorials applicable to your IdP. • If you are provisioning a primary email address, this attribute value must be unique for each user. In some IdPs, the primary email address might not be a real email address. For example, it might be a Universal Principal Name (UPN) that only looks like an email. These IdPs may have a secondary or “other” email address that contains the user’s real email address. You must conﬁgure SCIM in your IdP to map the non-Null unique email address to the IAM Identity Center primary email address attribute. And you must map the users non-Null unique sign-in identiﬁer to the IAM Identity Center user name attribute. Check to see whether your IdP has a single value that is both the sign-in identiﬁer and the user’s email name. If so, you can map that IdP ﬁeld to both the IAM Identity Center primary email and the IAM Identity Center user name. Manage an external identity provider 172 AWS IAM Identity Center User Guide • For SCIM synchronization to work, every user must have a First name, Last name, Username and Display name value speciﬁed. If any of these values are missing from a user, that user will not be provisioned. • If you need to use third-party applications, you will ﬁrst need to map the outbound SAML subject attribute to the user name attribute. If the third-party application needs a routable email address, you must provide the email attribute to your IdP. • SCIM provisioning and update intervals are controlled by your
sso-ug-074	sso-ug.pdf	74	an external identity provider 172 AWS IAM Identity Center User Guide • For SCIM synchronization to work, every user must have a First name, Last name, Username and Display name value speciﬁed. If any of these values are missing from a user, that user will not be provisioned. • If you need to use third-party applications, you will ﬁrst need to map the outbound SAML subject attribute to the user name attribute. If the third-party application needs a routable email address, you must provide the email attribute to your IdP. • SCIM provisioning and update intervals are controlled by your identity provider. Changes to users and groups in your identity provider are only reﬂected in IAM Identity Center after your identity provider sends those changes to IAM Identity Center. Check with your identity provider for details on the frequency of user and group updates. • Currently, multivalue attributes (such as multiple emails or phone numbers for a given user) are not provisioned with SCIM. Attempts to synchronize multivalue attributes into IAM Identity Center with SCIM will fail. To avoid failures, ensure that only a single value is passed for each attribute. If you have users with multivalue attributes, remove or modify the duplicate attribute mappings in SCIM at your IdP for the connection to IAM Identity Center. • Verify that the externalId SCIM mapping at your IdP corresponds to a value that is unique, always present, and least likely to change for your users. For example, your IdP might provide a guaranteed objectId or other identiﬁer that’s not aﬀected by changes to user attributes like name and email. If so, you can map that value to the SCIM externalId ﬁeld. This ensures that your users won’t lose AWS entitlements, assignments, or permissions if you need to change their name or email. • Users who have not yet been assigned to an application or AWS account cannot be provisioned into IAM Identity Center. To synchronize users and groups, make sure that they are assigned to the application or other setup that represents your IdP’s connection to IAM Identity Center. • User deprovisioning behavior is managed by the identity provider and may vary by their implementation. Check with your identity provider for details on user deprovisioning. • After setting up automatic provisioning with SCIM for your IdP, you can no longer add or edit users in the IAM Identity Center console. If you need to add or modify a user, you must do so from your external IdP or identity source. For more information about IAM Identity Center’s SCIM implementation, see the IAM Identity Center SCIM Implementation Developer Guide. Manage an external identity provider 173 AWS IAM Identity Center User Guide How to monitor access token expiry SCIM access tokens are generated with a validity of one year. When your SCIM access token is set to expire in 90 days or less, AWS sends you reminders in the IAM Identity Center console and over the AWS Health Dashboard to help you rotate the token. By rotating the SCIM access token before it expires, you continually secure automatic provisioning of user and group information. If the SCIM access token expires, the synchronization of user and group information from your identity provider into IAM Identity Center stops, so automatic provisioning can no longer make updates or create and delete information. Disruption to automatic provisioning may impose increased security risks and impact access to your services. The Identity Center console reminders persist until you rotate the SCIM access token and delete any unused or expired access tokens. The AWS Health Dashboard events are renewed weekly between 90 to 60 days, twice per week from 60 to 30 days, three times per week from 30 to 15 days, and daily from 15 days until the SCIM access tokens expires. Enable automatic provisioning Use the following procedure to enable automatic provisioning of users and groups from your IdP to IAM Identity Center using the SCIM protocol. Note Before you begin this procedure, we recommend that you ﬁrst review provisioning considerations that are applicable to your IdP. For more information, see the IAM Identity Center identity source tutorials for your IdP. To enable automatic provisioning in IAM Identity Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. Manage an external identity provider 174 AWS IAM Identity Center User Guide a. SCIM endpoint
sso-ug-075	sso-ug.pdf	75	Center 1. After you have completed the prerequisites, open the IAM Identity Center console. 2. Choose Settings in the left navigation pane. 3. On the Settings page, locate the Automatic provisioning information box, and then choose Enable. This immediately enables automatic provisioning in IAM Identity Center and displays the necessary SCIM endpoint and access token information. 4. In the Inbound automatic provisioning dialog box, copy the SCIM endpoint and access token. You'll need to paste these in later when you conﬁgure provisioning in your IdP. Manage an external identity provider 174 AWS IAM Identity Center User Guide a. SCIM endpoint - For example, https://scim.us- east-2.amazonaws.com/11111111111-2222-3333-4444-555555555555/scim/v2 b. Access token - Choose Show token to copy the value. Warning This is the only time where you can obtain the SCIM endpoint and access token. Ensure you copy these values before moving forward. You will enter these values to conﬁgure automatic provisioning in your IdP later in this tutorial. 5. Choose Close. After you complete this procedure, you must conﬁgure automatic provisioning in your IdP. For more information, see the IAM Identity Center identity source tutorials for your IdP. Disable automatic provisioning Use the following procedure to disable automatic provisioning in the IAM Identity Center console. Important You must delete the access token before you start this procedure. For more information, see Delete an access token. To disable automatic provisioning in the IAM Identity Center console 1. In the IAM Identity Center console, choose Settings in the left navigation pane. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Manage provisioning. 3. On the Automatic provisioning page, choose Disable. 4. In the Disable automatic provisioning dialog box, review the information, type DISABLE, and then choose Disable automatic provisioning. Manage an external identity provider 175 AWS IAM Identity Center Generate an access token User Guide Use the following procedure to generate a new access token in the IAM Identity Center console. Note This procedure requires that you have previously enabled automatic provisioning. For more information, see Enable automatic provisioning. To generate a new access token 1. In the IAM Identity Center console, choose Settings in the left navigation pane. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Manage provisioning. 3. On the Automatic provisioning page, under Access tokens, choose Generate token. 4. In the Generate new access token dialog box, copy the new access token and save it in a safe place. 5. Choose Close. Delete an access token Use the following procedure to delete an existing access token in the IAM Identity Center console. To to delete an existing access token 1. In the IAM Identity Center console, choose Settings in the left navigation pane. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Manage provisioning. 3. On the Automatic provisioning page, under Access tokens, select the access token you want to delete, and then choose Delete. 4. In the Delete access token dialog box, review the information, type DELETE, and then choose Delete access token. Manage an external identity provider 176 AWS IAM Identity Center Rotate an access token User Guide An IAM Identity Center directory supports up to two access tokens at a time. To generate an additional access token prior to any rotation, delete any expired or unused access tokens. If your SCIM access token is close to expiring, you can use the following procedure to rotate an existing access token in the IAM Identity Center console. To rotate an access token 1. In the IAM Identity Center console, choose Settings in the left navigation pane. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Manage provisioning. 3. On the Automatic provisioning page, under Access tokens, make a note of the token ID of the token you want to rotate. 4. Follow the steps in Generate an access token to create a new token. If you have already created the maximum number of SCIM access tokens, you will ﬁrst need to delete one of the existing tokens. 5. Go to your identity provider's website and conﬁgure the new access token for SCIM provisioning, and then test connectivity to IAM Identity Center using the new SCIM access token. Once you've conﬁrmed that provisioning is working successfully using the new token, continue to the next step in this procedure. 6. Follow the steps in Delete an access token to delete the old access token you noted earlier. You can also use the token’s creation date as a hint for which token to remove. Manual provisioning Some IdPs don't have System for Cross-domain Identity Management (SCIM) support or have an incompatible SCIM implementation. In those cases, you can manually provision users through the IAM Identity Center console. When
sso-ug-076	sso-ug.pdf	76	test connectivity to IAM Identity Center using the new SCIM access token. Once you've conﬁrmed that provisioning is working successfully using the new token, continue to the next step in this procedure. 6. Follow the steps in Delete an access token to delete the old access token you noted earlier. You can also use the token’s creation date as a hint for which token to remove. Manual provisioning Some IdPs don't have System for Cross-domain Identity Management (SCIM) support or have an incompatible SCIM implementation. In those cases, you can manually provision users through the IAM Identity Center console. When you add users to IAM Identity Center, ensure that you set the user name to be identical to the user name that you have in your IdP. At a minimum, you must have a unique email address and user name. For more information, see Username and email address uniqueness. You must also manage all groups manually in IAM Identity Center. To do this, you create the groups and add them using the IAM Identity Center console. These groups do not need to match what exists in your IdP. For more information, see Groups. Manage an external identity provider 177 AWS IAM Identity Center Rotate SAML 2.0 certiﬁcates User Guide IAM Identity Center uses certiﬁcates to set up a SAML trust relationship between IAM Identity Center and your external identity provider (IdP). When you add an external IdP in IAM Identity Center, you must also obtain at least one public SAML 2.0 X.509 certiﬁcate from the external IdP. That certiﬁcate is usually installed automatically during the IdP SAML metadata exchange during trust creation. As an IAM Identity Center administrator, you'll occasionally need to replace older IdP certiﬁcates with newer ones. For example, you might need to replace an IdP certiﬁcate when the expiration date on the certiﬁcate approaches. The process of replacing an older certiﬁcate with a newer one is referred to as certiﬁcate rotation. Topics • Rotate a SAML 2.0 certiﬁcate • Certiﬁcate expiration status indicators Rotate a SAML 2.0 certiﬁcate You may need to import certiﬁcates periodically in order to rotate invalid or expired certiﬁcates issued by your identity provider. This helps to prevent authentication disruption or downtime. All imported certiﬁcates are automatically active. Certiﬁcates should only be deleted after ensuring that they are no longer in use with the associated identity provider. You should also consider that some IdPs might not support multiple certiﬁcates. In this case, the act of rotating certiﬁcates with these IdPs might mean a temporary service disruption for your users. Service is restored when the trust with that IdP has been successfully reestablished. Plan this operation carefully during oﬀ peak hours if possible. Note As a security best practice, upon any signs of compromise or mishandling of an existing SAML certiﬁcate, you should immediately remove and rotate the certiﬁcate. Rotating an IAM Identity Center certiﬁcate is a multistep process that involves the following: • Obtaining a new certiﬁcate from the IdP Manage an external identity provider 178 AWS IAM Identity Center User Guide • Importing the new certiﬁcate into IAM Identity Center • Activating the new certiﬁcate in the IdP • Deleting the older certiﬁcate Use all of the following procedures to complete the certiﬁcate rotation process while avoiding any authentication downtime. Step 1: Obtain a new certiﬁcate from the IdP Go to the IdP website and download their SAML 2.0 certiﬁcate. Make sure that the certiﬁcate ﬁle is downloaded in PEM encoded format. Most providers allow you to create multiple SAML 2.0 certiﬁcates in the IdP. It is likely that these will be marked as disabled or inactive. Step 2: Import the new certiﬁcate into IAM Identity Center Use the following procedure to import the new certiﬁcate using the IAM Identity Center console. 1. In the IAM Identity Center console, choose Settings. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Manage authentication. 3. On the Manage SAML 2.0 certiﬁcates page, choose Import certiﬁcate. 4. On the Import SAML 2.0 certiﬁcate dialog, choose Choose ﬁle, navigate to your certiﬁcate ﬁle and select it, and then choose Import certiﬁcate. At this point, IAM Identity Center will trust all incoming SAML messages signed from both of the certiﬁcates that you have imported. Step 3: Activate the new certiﬁcate in the IdP Go back to the IdP website and mark the new certiﬁcate that you created earlier as primary or active. At this point all SAML messages signed by the IdP should be using the new certiﬁcate. Step 4: Delete the old certiﬁcate Use the following procedure to complete the certiﬁcate rotation process for your IdP. There must always be at least one valid certiﬁcate listed, and it cannot be removed. Manage an external identity provider 179 AWS IAM Identity
sso-ug-077	sso-ug.pdf	77	incoming SAML messages signed from both of the certiﬁcates that you have imported. Step 3: Activate the new certiﬁcate in the IdP Go back to the IdP website and mark the new certiﬁcate that you created earlier as primary or active. At this point all SAML messages signed by the IdP should be using the new certiﬁcate. Step 4: Delete the old certiﬁcate Use the following procedure to complete the certiﬁcate rotation process for your IdP. There must always be at least one valid certiﬁcate listed, and it cannot be removed. Manage an external identity provider 179 AWS IAM Identity Center Note User Guide Make sure that your identity provider is no longer signing SAML responses with this certiﬁcate before deleting it. 1. On the Manage SAML 2.0 certiﬁcates page, choose the certiﬁcate that you want to delete. Choose Delete. 2. In the Delete SAML 2.0 certiﬁcate dialog box, type DELETE to conﬁrm, and then choose Delete. 3. Return to the IdP’s website and perform the necessary steps to remove the older inactive certiﬁcate. Certiﬁcate expiration status indicators The Manage SAML 2.0 certiﬁcates page displays colored status indicator icons in the Expires on column next to each certiﬁcate in the list. The following describes the criteria that IAM Identity Center uses to determine which icon is displayed for each certiﬁcate. • Red – Indicates that a certiﬁcate is expired. • Yellow – Indicates that a certiﬁcate expires in 90 days or less. • Green – Indicates that a certiﬁcate is valid and remains valid for at least 90 more days. To check the current status of a certiﬁcate 1. In the IAM Identity Center console, choose Settings. 2. On the Settings page, choose the Identity source tab, and then choose Actions > Manage authentication. 3. On the Manage SAML 2.0 authentication page, under Manage SAML 2.0 certiﬁcates, review the status of the certiﬁcates in the list as indicated in the Expires on column. Using the AWS access portal The AWS access portal provides users with single sign-on access to all your AWS accounts and most commonly used cloud applications such as Oﬃce 365, Concur, Salesforce, and many more. Using the AWS access portal 180 AWS IAM Identity Center User Guide You can quickly launch multiple applications simply by choosing the AWS account or application icon in the portal. The presence of application icons in your AWS access portal means that an administrator from your company has granted you access to those AWS accounts or applications. It also means that you can access all these accounts or applications from the AWS access portal without additional sign-in prompts. Contact your administrator to request additional access in the following situations: • You don't see an AWS account or application that you need to access. • The access that you have to a given account or application isn't what you expected. Topics • Activating the AWS access portal for ﬁrst-time IAM Identity Center users • Signing in to the AWS access portal • Resetting your AWS access portal user password • Getting IAM Identity Center user credentials for the AWS CLI or AWS SDKs • Creating shortcut links to AWS Management Console destinations • Registering your device for MFA • Customizing the AWS access portal URL Activating the AWS access portal for ﬁrst-time IAM Identity Center users If this is your ﬁrst time attempting to sign in to the AWS access portal, check your email for instructions on how to activate your user credentials. To activate your user credentials 1. Depending on the email you received from your company, choose one of the following methods to activate your user credentials so that you can start using the AWS access portal. a. If you received an email with the subject Invitation to join AWS IAM Identity Center, open it and choose Accept invitation. On the New user sign up page, enter and conﬁrm a password, and then choose Set new password. You'll use that password each time you sign in to the portal. Activating the AWS access portal 181 AWS IAM Identity Center User Guide b. If you were sent an email from your company's IT support or IT administrator, follow the instructions they provided to activate your user credentials. 2. After you activate your user credentials by providing a new password, the AWS access portal signs you in automatically. If this doesn't occur, you can manually sign in to the AWS access portal by using the instructions provided in the next section. Signing in to the AWS access portal The AWS access portal provides IAM Identity Center users with single sign-on access to all their assigned AWS accounts and applications through a web portal. The following outlines how you can sign in to the AWS access portal, tips for signing in, and how to
sso-ug-078	sso-ug.pdf	78	to activate your user credentials. 2. After you activate your user credentials by providing a new password, the AWS access portal signs you in automatically. If this doesn't occur, you can manually sign in to the AWS access portal by using the instructions provided in the next section. Signing in to the AWS access portal The AWS access portal provides IAM Identity Center users with single sign-on access to all their assigned AWS accounts and applications through a web portal. The following outlines how you can sign in to the AWS access portal, tips for signing in, and how to sign out of the AWS access portal. To learn how to sign in the AWS access portal as an IAM Identity Center user, see Sign in to the AWS access portal in the AWS Sign-in Guide. Prerequisites IAM Identity Center needs to be enabled to use the AWS access portal. For more information, see Enable IAM Identity Center Note After you sign in, the default duration for your AWS access portal session is 8 hours. Be aware that an administrator can change the duration of this session. Sign in to the AWS access portal The following steps are for IAM Identity Center administrator to conﬁrm that the IAM Identity Center user can sign in to the AWS access portal and access the AWS account. Sign in to the AWS access portal 1. Do either of the following to sign in to the AWS Management Console. • New to AWS (root user) – Sign in as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. • Already using AWS (IAM credentials) – Sign in with your IAM credentials and select an admin role. Signing in to the AWS access portal 182 AWS IAM Identity Center User Guide 2. Open the IAM Identity Center console. 3. In the navigation pane, choose Dashboard. 4. On the Dashboard page, under Settings summary, choose the AWS access portal URL. 5. Sign in by using either of the following: • If you're using Active Directory or an external identity provider (IdP) as your identity source, sign in by using the credentials of the Active Directory or IdP user. • If you're using the default Identity Center directory as your identity source, sign in by using the username that you speciﬁed when you created the user and the new password that you speciﬁed for the user. In the Accounts tab, locate your AWS account and expand it. The roles available to you are displayed. For example, if you're assigned both the AdministratorAccess permission set and Billing permissions sets, those roles are displayed in the AWS access portal. Choose the IAM role name you want to use for the session. 6. 7. 8. If you're redirected to the AWS Management Console you successfully ﬁnished setting up access to the AWS account. Note If you don't see any AWS accounts listed, it's likely that the user hasn't yet been assigned to a permission set for that account. For instructions on assigning users to a permission set, see Assign user or group access to AWS accounts. Now that you've conﬁrmed that you can sign in using IAM Identity Center credentials, switch to the browser that you used to sign into the AWS Management Console and sign out from your root user or IAM user credentials. Important We strongly recommend that you use the credentials of the IAM Identity Center administrative user when you sign in to the AWS access portal to perform administrative tasks instead of using IAM user or root user credentials. Safeguard your root user credentials and use them to perform the tasks that only the root user can perform. To enable other users to access your accounts and applications, and to administer IAM Identity Center, create and assign permission sets only through IAM Identity Center. Signing in to the AWS access portal 183 AWS IAM Identity Center Trusted devices User Guide When you choose the option This is a trusted device from the sign-in page, IAM Identity Center considers all future sign-ins from that device as authorized. This means that IAM Identity Center won't present an option to enter in an MFA code as long as you're using that trusted device. However, there are some exceptions, including signing in from a new browser or when your device has been issued an unknown IP address. Sign in tips for the AWS access portal Here are some tips to help you manage your AWS access portal experience. • Occasionally, you might need to sign out and sign back in to the AWS access portal. This might be necessary to access new applications that your administrator recently assigned to you. This is not required, however, because all new
sso-ug-079	sso-ug.pdf	79	an option to enter in an MFA code as long as you're using that trusted device. However, there are some exceptions, including signing in from a new browser or when your device has been issued an unknown IP address. Sign in tips for the AWS access portal Here are some tips to help you manage your AWS access portal experience. • Occasionally, you might need to sign out and sign back in to the AWS access portal. This might be necessary to access new applications that your administrator recently assigned to you. This is not required, however, because all new applications are refreshed every hour. • When you sign in to the AWS access portal, you can open any of the applications listed in the portal by choosing the application’s icon. After you are done using the application, you can either close the application or sign out of the AWS access portal. Closing the application signs you out of that application only. Any other applications that you have opened from the AWS access portal remain open and running. • Before you can sign in as a diﬀerent user, you must ﬁrst sign out of the AWS access portal. Signing out from the portal completely removes your credentials from the browser session. • Once you sign in to the AWS access portal, you can switch to a role. Switching roles temporarily sets aside your original user permissions and instead gives you the permissions assigned to the role. For more information, see Switching to a role (console). Signing out of the AWS access portal When you sign out from the portal, your credentials are completely removed from the browser session. For more information, see Sign out of the AWS access portal in the AWS Sign-In guide. To sign out of the AWS access portal • In the AWS access portal, choose Sign out from the navigation bar. Signing in to the AWS access portal 184 AWS IAM Identity Center Note User Guide If you want to sign in as a diﬀerent user, you must ﬁrst sign out of the AWS access portal. Resetting your AWS access portal user password The AWS access portal provides IAM Identity Center users with single sign-on access to all their assigned AWS accounts and cloud applications through a web portal. The AWS access portal is diﬀerent from the AWS Management Console, which is a collection of service consoles for managing AWS resources. Use this procedure to reset your IAM Identity Center user password for the AWS access portal. Learn more about User types in the AWS Sign-In User Guide. Considerations The reset your password functionality for your AWS access portal is only available for users of Identity Center instances that are using Identity Center directory or AWS Managed Microsoft AD as their identity source. If your user is connected to an external identity provider or AD Connector, user password resets must be done from the external identity provider or connected Active Directory. • If your identity source is an IAM Identity Center directory, see Password requirements when managing identities in IAM Identity Center. • If your identity source is an AWS Managed Microsoft AD, see Password requirements when resetting a password in AWS Managed Microsoft AD. To reset your password to the AWS access portal 1. Open a web browser and go to the sign-in page for your AWS access portal. If you don't have your AWS access portal URL, check your email. You should have been emailed an invitation to join AWS IAM Identity Center that includes a speciﬁc sign-in URL to the AWS access portal. Alternatively, your administrator might have directly provided you with a one- time password and the AWS access portal URL. If you can't locate this information, ask your administrator to send it to you. Resetting your user password 185 AWS IAM Identity Center User Guide For more information about signing into the AWS access portal, see Sign in to the AWS access portal in the AWS Sign-In User Guide. 2. Enter your Username, and then choose Next. 3. Under Password, choose Forgot password. Verify your Username and enter the characters for the provided image to conﬁrm that you're not a robot. Then choose Next. You might need to disable ad blocker software if you can't enter characters. 4. A message appears to conﬁrm that a reset password email was sent. Choose Continue. 5. You'll receive an email from [email protected] with the subject Password reset requested. In your email, choose Reset password. 6. On the Reset password page, verify your Username, specify a new password for the AWS access portal, and then choose Set new password. 7. You'll receive an email from [email protected] with the subject line Password updated. Note An administrator can reset your password by either sending an email to
sso-ug-080	sso-ug.pdf	80	Then choose Next. You might need to disable ad blocker software if you can't enter characters. 4. A message appears to conﬁrm that a reset password email was sent. Choose Continue. 5. You'll receive an email from [email protected] with the subject Password reset requested. In your email, choose Reset password. 6. On the Reset password page, verify your Username, specify a new password for the AWS access portal, and then choose Set new password. 7. You'll receive an email from [email protected] with the subject line Password updated. Note An administrator can reset your password by either sending an email to you with instructions for resetting your password or generating a one-time password and sharing it with you. If you're an administrator, see Reset the IAM Identity Center user password for an end user. Getting IAM Identity Center user credentials for the AWS CLI or AWS SDKs You can access AWS services programmatically by using the AWS Command Line Interface or AWS Software Development Kits (SDKs) with user credentials from IAM Identity Center. This topic describes how to get temporary credentials for a user in IAM Identity Center. The AWS access portal provides IAM Identity Center users with single-sign on access to their AWS accounts and cloud applications. After you sign in to the AWS access portal as an IAM Identity Center user, you can get temporary credentials. You can then use the credentials, also referred to as IAM Identity Center user credentials, in the AWS CLI or AWS SDKs to access resources in an AWS account. AWS CLI and AWS SDK access 186 AWS IAM Identity Center User Guide If you’re using the AWS CLI to access AWS services programmatically, you can use the procedures in this topic to initiate access to the AWS CLI. For information about the AWS CLI, see the AWS Command Line Interface User Guide. If you’re using the AWS SDKs to access AWS services programmatically, following the procedures in this topic also directly establishes authentication for the AWS SDKs. For information about the AWS SDKs, see the AWS SDKs and Tools Reference Guide. Note Users in IAM Identity Center are diﬀerent than IAM users. IAM users are granted long- term credentials to AWS resources. Users in IAM Identity Center are granted temporary credentials. We recommend that you use temporary credentials as a security best practice for accessing your AWS accounts because these credentials are generated every time you sign in. Prerequisites To get temporary credentials for your IAM Identity Center user, you'll need the following: • An IAM Identity Center user – You'll sign in to the AWS access portal as this user. You or your administrator might create this user. For information about how to enable IAM Identity Center and create an IAM Identity Center user, see Getting started with IAM Identity Center. • User access to an AWS account – To grant an IAM Identity Center user permission to retrieve their temporary credentials, you or an administrator must assign the IAM Identity Center user to a permission set. Permission sets are stored in IAM Identity Center and deﬁne the level of access that an IAM Identity Center user has to an AWS account. If your administrator created the IAM Identity Center user for you, ask them to add this access for you. For more information, see Assign user or group access to AWS accounts. • AWS CLI installed – To use the temporary credentials, you must install the AWS CLI. For instructions, see Installing or updating the latest version of the AWS CLI in the AWS CLI User Guide. Considerations Before you complete the steps to get temporary credentials for your IAM Identity Center user, keep the following considerations in mind: AWS CLI and AWS SDK access 187 AWS IAM Identity Center User Guide • IAM Identity Center creates IAM roles – When you assign a user in IAM Identity Center to a permission set, IAM Identity Center creates a corresponding IAM role from the permission set. IAM roles created by permission sets diﬀer from IAM roles created in AWS Identity and Access Management in the following ways: • IAM Identity Center owns and secures the roles that are created by permission sets. Only IAM Identity Center can modify these roles. • Only users in IAM Identity Center can assume the roles that correspond to their assigned permission sets. You can’t assign permission set access to IAM users, IAM federated users, or service accounts. • You can’t modify a role trust policy on these roles to allow access to principals outside of IAM Identity Center. For information about how to get temporary credentials for a role that you create in IAM, see Using temporary security credentials with the AWS CLI in the AWS Identity and Access Management User Guide. • You can set
sso-ug-081	sso-ug.pdf	81	Only IAM Identity Center can modify these roles. • Only users in IAM Identity Center can assume the roles that correspond to their assigned permission sets. You can’t assign permission set access to IAM users, IAM federated users, or service accounts. • You can’t modify a role trust policy on these roles to allow access to principals outside of IAM Identity Center. For information about how to get temporary credentials for a role that you create in IAM, see Using temporary security credentials with the AWS CLI in the AWS Identity and Access Management User Guide. • You can set the session duration for permission sets – After you sign in to the AWS access portal, the permission set to which your IAM Identity Center user is assigned appears as an available role. IAM Identity Center creates a separate session for this role. This session can be from one to 12 hours, depending the session duration conﬁgured for the permission set. The default session duration is one hour. For more information, see Set session duration for AWS accounts. Getting and refreshing temporary credentials You can get and refresh temporary credentials for your IAM Identity Center user automatically or manually. Topics • Automatic credential refresh (recommended) • Manual credential refresh Automatic credential refresh (recommended) Automatic credential refresh uses the Open ID Connect (OIDC) Device Code Authorization standard. With this method, you initiate access directly by using the aws configure sso command in the AWS CLI and AWS SDK access 188 AWS IAM Identity Center User Guide AWS CLI. You can use this command to automatically access any role that's associated with any permission set that you’re assigned to for any AWS account. To access the role created for your IAM Identity Center user, run the aws configure sso command, and then authorize the AWS CLI from a browser window. As long as you have an active AWS access portal session, the AWS CLI automatically retrieves temporary credentials and refreshes the credentials automatically. For more information, see Conﬁgure your proﬁle with the aws configure sso wizard in the AWS Command Line Interface User Guide. To get temporary credentials that automatically refresh 1. Sign in to the AWS access portal by using the speciﬁc sign-in URL provided by your administrator. If you created the IAM Identity Center user, AWS sent an email invitation that includes your sign-in URL. For more information, see Sign in to the AWS access portal in the AWS Sign-In User Guide. 2. In the Accounts tab, locate the AWS account from which you want to retrieve credentials. When you choose the account, the account name, account ID, and email address associated with the account appear. Note If you don't see any AWS accounts listed, it's likely that you've not yet been assigned to a permission set for that account. In this case, contact your administrator and ask them to add this access for you. For more information, see Assign user or group access to AWS accounts. 3. Below the name of the account, the permission set to which your IAM Identity Center user is assigned appears as an available role. For example, if your IAM Identity Center user is assigned to the PowerUserAccess permission set for the account, the role appears in the AWS access portal as PowerUserAccess. 4. Depending on your option next to the role name, either choose Access keys or choose Command line or programmatic access. 5. In the Get credentials dialog box, choose either macOS and Linux, Windows, or PowerShell, depending on the operating system on which you installed the AWS CLI. 6. Under AWS IAM Identity Center credentials (Recommended), your SSO Start URL and SSO Region are displayed. These values are required to conﬁgure both an IAM Identity Center AWS CLI and AWS SDK access 189 AWS IAM Identity Center User Guide enabled proﬁle and sso-session to your AWS CLI. To complete this conﬁguration, follow the instructions in Conﬁgure your proﬁle with the aws configure sso wizard in the AWS Command Line Interface User Guide. Continue using the AWS CLI as necessary for your AWS account until the credentials have expired. Manual credential refresh You can use the manual credential refresh method to get temporary credentials for a role that's associated with a speciﬁc permission set in a speciﬁc AWS account. To do so, you copy and paste the required commands for the temporary credentials. With this method, you must refresh the temporary credentials manually. You can run AWS CLI commands until your temporary credentials expire. To get credentials that you manually refresh 1. Sign in to the AWS access portal by using the speciﬁc sign-in URL provided by your administrator. If you created the IAM Identity Center user, AWS sent an email invitation that includes your sign-in URL. For more information, see Sign
sso-ug-082	sso-ug.pdf	82	temporary credentials for a role that's associated with a speciﬁc permission set in a speciﬁc AWS account. To do so, you copy and paste the required commands for the temporary credentials. With this method, you must refresh the temporary credentials manually. You can run AWS CLI commands until your temporary credentials expire. To get credentials that you manually refresh 1. Sign in to the AWS access portal by using the speciﬁc sign-in URL provided by your administrator. If you created the IAM Identity Center user, AWS sent an email invitation that includes your sign-in URL. For more information, see Sign in to the AWS access portal in the AWS Sign-In User Guide. 2. In the Accounts tab, locate the AWS account from which you want to retrieve access credentials and expand it to show the IAM role name (for example Administrator). Depending on your option next to the IAM role name, either choose Access keys or choose Command line or programmatic access. Note If you don't see any AWS accounts listed, it's likely that you've not yet been assigned to a permission set for that account. In this case, contact your administrator and ask them to add this access for you. For more information, see Assign user or group access to AWS accounts. 3. In the Get credentials dialog box, choose MacOS and Linux, Windows, or PowerShell, depending on the operating system on which you installed the AWS CLI. 4. Choose any of the following options: • Option 1: Set AWS environment variables AWS CLI and AWS SDK access 190 AWS IAM Identity Center User Guide Choose this option to override all credential settings, including any settings in the credentials ﬁles and config ﬁles. For more information, see Environment variables to conﬁgure the AWS CLI in the AWS CLI User Guide. To use this option, copy the commands to your clipboard, paste the commands into your AWS CLI terminal window, and then press Enter to set the required environment variables. • Option 2: Add a proﬁle to your AWS credentials ﬁle Choose this option to run commands with diﬀerent sets of credentials. To use this option, copy the commands to your clipboard, and then paste the commands into your shared AWS credentials ﬁle to set up a new named proﬁle. For more information, see Shared conﬁg and credentials ﬁles in the AWS SDKs and Tools Reference Guide. To use this credential, specify the --profile option in your AWS CLI command. This aﬀects all environments that use the same credential ﬁle. • Option 3: Use individual values in your AWS service client Choose this option to access AWS resources from an AWS service client. For more information, see Tools to Build on AWS. To use this option, copy the values to your clipboard, paste the values into your code, and assign them to the appropriate variables for your SDK. For more information, see the documentation for your speciﬁc SDK API. Creating shortcut links to AWS Management Console destinations Shortcut links created in the AWS access portal take IAM Identity Center users to a speciﬁc destination in the AWS Management Console, with a speciﬁc permission set, and in a speciﬁc AWS account. Shortcut links save time for you and your collaborators. Instead of navigating to a desired destination URL in the AWS Management Console (for example, an Amazon S3 bucket instance page) through multiple pages, including AWS access portal, you can use a shortcut link to get to the same destination automatically. Shortcut link destination options Shortcut links have three destination options, listed here by priority: Creating shortcut links 191 AWS IAM Identity Center User Guide • (Optional) Any destination URL in the AWS Management Console speciﬁed in the shortcut link. For example, the Amazon S3 bucket instance page. • (Optional) Administrator-conﬁgured relay state URL for the permission set in question. For more information about setting the relay state, see Set relay state for quick access to the AWS Management Console. • AWS Management Console home. The default destination if you don't specify one. Note Automatic navigation to a destination is successful only when you’re authenticated with IAM Identity Center and have the necessary permission set assigned for the AWS account and destination URL. The AWS access portal includes a Create shortcut button that helps you create a shareable shortcut link. If you plan to specify a destination URL (the ﬁrst option in the previous list), you can copy the URL to a clipboard to share it. Create a shortcut link in the AWS access portal 1. While signed into the AWS access portal, choose the Accounts tab and then choose the Create shortcut button. 2. In the dialog box: a. Choose an AWS account using the account ID or account name. As you type, a drop-down menu displays matching account IDs
sso-ug-083	sso-ug.pdf	83	destination URL. The AWS access portal includes a Create shortcut button that helps you create a shareable shortcut link. If you plan to specify a destination URL (the ﬁrst option in the previous list), you can copy the URL to a clipboard to share it. Create a shortcut link in the AWS access portal 1. While signed into the AWS access portal, choose the Accounts tab and then choose the Create shortcut button. 2. In the dialog box: a. Choose an AWS account using the account ID or account name. As you type, a drop-down menu displays matching account IDs and names that you can access. You can choose only an account to which you have access. b. Optionally choose an IAM role from the drop-down list. These are the permission sets assigned to you for the selected account. If you omit choosing the role, users are prompted to select one assigned to them for the chosen account when using the shortcut link. Note You can't grant new access with shortcut links. Shortcut links work only with the permission sets already assigned to the user. If the user doesn't have the necessary Creating shortcut links 192 AWS IAM Identity Center User Guide permission sets assigned for the account and destination URL, they're denied access. c. Optionally enter the AWS access portal destination URL. If you omit entering a URL, the destination is automatically determined when using the shortcut link, based on the previously-mentioned shortcut link destination options. d. Your shortcut link generates at the bottom of the dialog box, based on your input. Choose the Copy URL button. You can now create a bookmark with the copied shortcut link or share it with your collaborators who have access to the same account with the same permission set or another suﬃcient permission set. Constructing secure AWS Management Console shortcut links with URL encoding All parameter values of the URL, including the account ID, permission set name, and destination URL, must be URL-encoded. Shortcut links extend the AWS access portal URL with the following path: /#/console? account_id=[account_ID]&role_name=[permission_set_name]&destination=[destination_URL] The full URL in the classic AWS partition follows this pattern: https://[your_subdomain].awsapps.com/start/#/console? account_id=[account_ID]&role_name=[permission_set_name]&destination=[destination_URL] Here's an example shortcut link that signs a user into account 123456789012 with the S3FullAccess permission set, and takes them to the S3 console home page: • https://example.awsapps.com/start/#/console? account_id=123456789012&role_name=S3FullAccess&destination=https%3A%2F %2Fconsole.aws.amazon.com%2Fs3%2Fhome • (AWS GovCloud (US) Region) https://start.us-gov-west-1.us- gov-home.awsapps.com/directory/example/#/console? account_id=123456789012&role_name=S3FullAccess&destination=https%3A%2F %2Fconsole.amazonaws-us-gov.com%2Fs3%2Fhome Creating shortcut links 193 AWS IAM Identity Center User Guide Registering your device for MFA Use the following procedure within the AWS access portal to register your new device for multi- factor authentication (MFA). Note We recommend that you ﬁrst download the appropriate Authenticator app onto your device before starting the steps in this procedure. For a list of apps that you can use for MFA devices, see Virtual authenticator apps. To register your device for use with MFA 1. Sign in to your AWS access portal. For more information, see Signing in to the AWS access portal. 2. Near the top-right of the page, choose MFA devices. 3. On the Multi-factor authentication (MFA) devices page, choose Register device. Note If the Register MFA device option is grayed out, contact your administrator for assistance with registering your device. 4. On the Register MFA device page, select one of the following MFA device types, and follow the instructions: • Authenticator app 1. On the Set up the authenticator app page, you might notice conﬁguration information for the new MFA device, including a QR code graphic. The graphic is a representation of the secret key that's available for manual entry on devices that don't support QR codes. 2. Using the physical MFA device, do the following: a. Open a compatible MFA authenticator app. For a list of tested apps that you can use with MFA devices, see Virtual authenticator apps. If the MFA app supports multiple accounts (multiple MFA devices), choose the option to create a new account (a new MFA device). Registering your device for MFA 194 AWS IAM Identity Center User Guide b. Determine whether the MFA app supports QR codes, and then do one of the following on the Set up the authenticator app page: i. Choose Show QR code, and then use the app to scan the QR code. For example, you might choose the camera icon or choose an option similar to Scan code. Then use the device's camera to scan the code. ii. Choose show secret key, and then enter that secret key into your MFA app. Important When you conﬁgure an MFA device for IAM Identity Center, we recommend that you save a copy of the QR code or secret key in a secure place. This can help if you lose the phone or have to reinstall the MFA authenticator app. If either of those things happen, you
sso-ug-084	sso-ug.pdf	84	use the app to scan the QR code. For example, you might choose the camera icon or choose an option similar to Scan code. Then use the device's camera to scan the code. ii. Choose show secret key, and then enter that secret key into your MFA app. Important When you conﬁgure an MFA device for IAM Identity Center, we recommend that you save a copy of the QR code or secret key in a secure place. This can help if you lose the phone or have to reinstall the MFA authenticator app. If either of those things happen, you can quickly reconﬁgure the app to use the same MFA conﬁguration. 3. On the Set up the authenticator app page, under Authenticator code, enter the one- time password that currently appears on the physical MFA device. Important Submit your request immediately after generating the code. If you generate the code and then wait too long to submit the request, the MFA device is successfully associated with your user, but the MFA device is out of sync. This happens because time-based one-time passwords (TOTP) expire after a short period of time. If this happens, you can sync the device again. 4. Choose Assign MFA. The MFA device can now start generating one-time passwords and is now ready for use with AWS. • Security key or Built-in authenticator 1. On the Register your user's security key page, follow the instructions provided by your browser or platform. Note The experience varies based on the browser or platform. After your device is successfully registered, you can associate a friendly display name with your newly Registering your device for MFA 195 AWS IAM Identity Center User Guide enrolled device. To to change the name, choose Rename, enter the new name, and then choose Save. Customizing the AWS access portal URL By default, you can access the AWS access portal by using a URL that follows this format: d-xxxxxxxxxx.awsapps.com/start. You can customize the URL as follows: your_subdomain.awsapps.com/start. Important If you change the AWS access portal URL, you can't edit it later. To customize your URL 1. Open the AWS IAM Identity Center console at https://console.aws.amazon.com/singlesignon/. 2. In the IAM Identity Center console, choose Dashboard in the navigation pane and locate the Settings summary section. 3. Choose the Customize button below your AWS access portal URL. Note If the Customize button doesn't display, it means that the AWS access portal has already been customized. Customizing the AWS access portal URL is a one-time operation that can't be reversed. 4. Enter your desired subdomain name and choose Save. You can now sign in to the AWS Console through your AWS access portal with your customized URL. Customizing the AWS access portal URL 196 AWS IAM Identity Center User Guide Multi-factor authentication for Identity Center users IAM Identity Center comes preconﬁgured with multi-factor authentication (MFA) turned on by default so that all users must sign in with MFA in addition to their user name and password. This ensures that users must sign in to the AWS access portal using the following two factors: • Their user name and password. This is the ﬁrst factor and is something users know. • Either a code, security key, or biometrics. This is the second factor and is something users have (possession) or are (biometric). The second factor might be either an authentication code generated from their mobile device, a security key connected to their computer, or user’s biometric scan. Together, these multiple factors provide increased security by preventing unauthorized access to your AWS resources unless a valid MFA challenge has been successfully completed. Each user can register up to two virtual authenticator apps, which are one-time password authenticator applications installed on your mobile device or tablet, and six FIDO authenticators, which include built-in authenticators and security keys, for a total of eight MFA devices. Learn more about Available MFA types for IAM Identity Center. Topics • Available MFA types for IAM Identity Center • Conﬁgure MFA in IAM Identity Center • Register an MFA device for users • Renaming and deleting MFA devices in IAM Identity Center Available MFA types for IAM Identity Center Multi-factor authentication (MFA) is a simple and eﬀective mechanism to enhance the security of your users. A user’s ﬁrst factor — their password — is a secret that they memorize, also known as a knowledge factor. Other factors can be possession factors (something you have, such as a security key) or inherence factors (something you are, such as a biometric scan). We strongly recommend that you conﬁgure MFA to add an additional layer of security to your account. IAM Identity Center MFA supports the following device types. All MFA types are supported for both browser-based console access as well as using the AWS CLI v2 with IAM Identity
sso-ug-085	sso-ug.pdf	85	mechanism to enhance the security of your users. A user’s ﬁrst factor — their password — is a secret that they memorize, also known as a knowledge factor. Other factors can be possession factors (something you have, such as a security key) or inherence factors (something you are, such as a biometric scan). We strongly recommend that you conﬁgure MFA to add an additional layer of security to your account. IAM Identity Center MFA supports the following device types. All MFA types are supported for both browser-based console access as well as using the AWS CLI v2 with IAM Identity Center. Multi-factor authentication 197 AWS IAM Identity Center User Guide • FIDO2 authenticators, including built-in authenticators and security keys • Virtual authenticator apps • Your own RADIUS MFA implementation connected through AWS Managed Microsoft AD A user can have up to eight MFA devices, which include up to two virtual authenticator apps and six FIDO authenticators, registered to one AWS account. You can also conﬁgure MFA settings to require MFA whenever they attempt to sign-in from a new device or browser, or when signing in from an unknown IP address. For more information about how to conﬁgure MFA settings for your users, see Choose MFA types for user authentication and Conﬁgure MFA device enforcement. FIDO2 authenticators FIDO2 is a standard that includes CTAP2 and WebAuthn and is based on public key cryptography. FIDO credentials are phishing-resistant because they are unique to the website that the credentials were created such as AWS. AWS supports the two most common form factors for FIDO authenticators: built-in authenticators and security keys. See below for more information about the most common types of FIDO authenticators. Topics • Built-in authenticators • Security keys • Password managers, passkey providers, and other FIDO authenticators Built-in authenticators Many modern computers and mobile phones have built-in authenticators, such as TouchID on Macbook or a Windows Hello-compatible camera. If your device has a FIDO-compatible built-in authenticator, you can use your ﬁngerprint, face, or device pin as a second factor. Security keys Security keys are FIDO-compatible external hardware authenticators that you can purchase and connect to your device through USB, BLE, or NFC. When you’re prompted for MFA, you simply complete a gesture with the key’s sensor. Some examples of security keys include YubiKeys and Available MFA types 198 AWS IAM Identity Center User Guide Feitian keys, and the most common security keys create device-bound FIDO credentials. For a list of all FIDO-certiﬁed security keys, see FIDO Certiﬁed Products. Password managers, passkey providers, and other FIDO authenticators Multiple third party providers support FIDO authentication in mobile applications, as features in password managers, smart cards with a FIDO mode, and other form factors. These FIDO- compatible devices can work with IAM Identity Center, but we recommend that you test a FIDO authenticator yourself before enabling this option for MFA. Note Some FIDO authenticators can create discoverable FIDO credentials known as passkeys. Passkeys may be bound to the device that creates them, or they may be syncable and backed up to a cloud. For example, you can register a passkey using Apple Touch ID on a supported Macbook, and then log in to a site from a Windows laptop using Google Chrome with your passkey in iCloud by following the on-screen prompts at sign-in. For more information about which devices support syncable passkeys and current passkey interoperability between operating systems and browsers, see Device Support at passkeys.dev, a resource maintained by the FIDO Alliance And World Wide Web Consortium (W3C). Virtual authenticator apps Authenticator apps are essentially one-time password (OTP)–based third party-authenticators. You can use an authenticator application installed on your mobile device or tablet as an authorized MFA device. The third-party authenticator application must be compliant with RFC 6238, which is a standards-based time-based one-time password (TOTP) algorithm capable of generating six-digit authentication codes. When prompted for MFA, users must enter a valid code from their authenticator app within the input box presented. Each MFA device assigned to a user must be unique. Two authenticator apps can be registered for any given user. Tested authenticator apps Any TOTP-compliant application will work with IAM Identity Center MFA. The following table lists well-known third-party authenticator apps to choose from. Available MFA types 199 AWS IAM Identity Center User Guide Operating system Tested authenticator app Android iOS RADIUS MFA Authy, Duo Mobile, Microsoft Authenticator, Google Authenticator Authy, Duo Mobile, Microsoft Authenticator, Google Authenticator Remote Authentication Dial-In User Service (RADIUS) is an industry-standard client-server protocol that provides authentication, authorization, and accounting management so users can connect to network services. AWS Directory Service includes a RADIUS client that connects to the RADIUS server upon which you have implemented your MFA solution. For more information, see Enable Multi-Factor Authentication for AWS Managed Microsoft AD. You can use either RADIUS
sso-ug-086	sso-ug.pdf	86	apps to choose from. Available MFA types 199 AWS IAM Identity Center User Guide Operating system Tested authenticator app Android iOS RADIUS MFA Authy, Duo Mobile, Microsoft Authenticator, Google Authenticator Authy, Duo Mobile, Microsoft Authenticator, Google Authenticator Remote Authentication Dial-In User Service (RADIUS) is an industry-standard client-server protocol that provides authentication, authorization, and accounting management so users can connect to network services. AWS Directory Service includes a RADIUS client that connects to the RADIUS server upon which you have implemented your MFA solution. For more information, see Enable Multi-Factor Authentication for AWS Managed Microsoft AD. You can use either RADIUS MFA or MFA in IAM Identity Center for user sign-ins to the user portal, but not both. MFA in IAM Identity Center is an alternative to RADIUS MFA in cases where you want AWS native two-factor authentication for access to the portal. When you enable MFA in IAM Identity Center, your users need an MFA device to sign in to the AWS access portal. If you had previously used RADIUS MFA, enabling MFA in IAM Identity Center eﬀectively overrides RADIUS MFA for users who sign in to the AWS access portal. However, RADIUS MFA continues to challenge users when they sign in to all other applications that work with AWS Directory Service, such as Amazon WorkDocs. If your MFA is Disabled on the IAM Identity Center console and you have conﬁgured RADIUS MFA with AWS Directory Service, RADIUS MFA governs AWS access portal sign-in. This means that IAM Identity Center falls back to RADIUS MFA conﬁguration if MFA is disabled. Conﬁgure MFA in IAM Identity Center You can conﬁgure MFA capabilities in IAM Identity Center when your identity source is conﬁgured with IAM Identity Center’s identity store, AWS Managed Microsoft AD, or AD Connector. MFA in IAM Identity Center is currently not supported for external identity providers. The following are general MFA recommendations, depending on your IAM Identity Center settings and organizational preferences. Conﬁgure MFA 200 AWS IAM Identity Center User Guide • Users are encouraged to register multiple backup authenticators for all enabled MFA types. This practice can prevent loss of access in case of a broken or misplaced MFA device. • Don't choose the Require Them to Provide a One-Time Password Sent by Email option if your users must sign in to the AWS access portal to access their email. For example, your users might use Microsoft 365 in the AWS access portal to read their email. In this case, users won't be able to retrieve the veriﬁcation code and would be unable to sign in to the AWS access portal. For more information, see Conﬁgure MFA device enforcement. • If you're already using RADIUS MFA that you conﬁgured with AWS Directory Service, you don't need to enable MFA within IAM Identity Center. MFA in IAM Identity Center is an alternative to RADIUS MFA for Microsoft Active Directory users of IAM Identity Center. For more information, see RADIUS MFA. • The following YouTube video provides an overview of MFA and IAM Identity Center: IAM Identity Center: Multi-factor authentication defaults for new instances Topics • Prompt users for MFA • Choose MFA types for user authentication • Conﬁgure MFA device enforcement • Allow users to register their own MFA devices Prompt users for MFA You can use the following steps to determine how often workforce users are prompted for multi- factor authentication (MFA) whenever they attempt to sign-in to the AWS access portal. Before you begin, we recommend that you understand the Available MFA types for IAM Identity Center. Important The instructions in this section apply to AWS IAM Identity Center. They do not apply to AWS Identity and Access Management (IAM). IAM Identity Center users, groups, and user credentials are diﬀerent from IAM users, groups, and IAM user credentials. If you are looking for instructions on deactivating MFA for IAM users, see Deactivating MFA devices in the AWS Identity and Access Management User Guide. Conﬁgure MFA 201 AWS IAM Identity Center Note User Guide If you’re using an external IdP, the Multi-factor authentication section won't be available. Your external IdP manages MFA settings, rather than IAM Identity Center managing them. To conﬁgure MFA 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Multi-factor authentication section, choose Conﬁgure. 5. On the Conﬁgure multi-factor authentication page, under Prompt users for MFA, choose one of the following authentication modes based on the level of security that your business needs: • Every time they sign in (always-on) In this mode (the default setting), IAM Identity Center requires that users with a registered MFA device will be prompted every time they sign in. This is the most secure setting and ensures that your organizational or
sso-ug-087	sso-ug.pdf	87	Center console. 2. In the left navigation pane, choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Multi-factor authentication section, choose Conﬁgure. 5. On the Conﬁgure multi-factor authentication page, under Prompt users for MFA, choose one of the following authentication modes based on the level of security that your business needs: • Every time they sign in (always-on) In this mode (the default setting), IAM Identity Center requires that users with a registered MFA device will be prompted every time they sign in. This is the most secure setting and ensures that your organizational or compliance policies are enforced by requiring that MFA be used every time they sign in to the AWS access portal. For example, PCI DSS strongly recommends MFA during every sign-in to access applications that support high-risk payment transactions. • Only when their sign-in context changes (context-aware) In this mode, IAM Identity Center provides users the option to trust their device during sign- in. After a user indicates that they want to trust a device, IAM Identity Center prompts the user for MFA once and analyzes the sign-in context (such as device, browser, and location) for the user’s subsequent sign-ins. For subsequent sign-ins, IAM Identity Center determines if the user is signing in with a previously trusted context. If the user’s sign-in context changes, IAM Identity Center prompts the user for MFA in addition to their email address and password credentials. This mode provides ease of use for users who frequently sign in from their workplace but is less secure then the always-on option. Users are only prompted for MFA if their sign-in context changes. • Never (disabled) Conﬁgure MFA 202 AWS IAM Identity Center User Guide While in this mode, all users will sign in with their standard user name and password only. Choosing this option disables IAM Identity Center MFA and is not recommended. While MFA is disabled for your Identity Center directory for users, you can't manage MFA devices in their user details, and Identity Center directory users can't manage MFA devices from the AWS access portal. Note If you are already using RADIUS MFA with AWS Directory Service, and want to continue using it as your default MFA type, then you can leave the authentication mode as disabled to bypass MFA capabilities in IAM Identity Center. Changing from Disabled mode to Context-aware or Always-on mode will override the existing RADIUS MFA settings. For more information, see RADIUS MFA. 6. Choose Save changes. Related Topics • Choose MFA types for user authentication • Conﬁgure MFA device enforcement • Allow users to register their own MFA devices Choose MFA types for user authentication Use the following procedure to choose the device types your users can authenticate with when prompted for MFA in the AWS access portal. To conﬁgure MFA types for your users 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Multi-factor authentication section, choose Conﬁgure. 5. On the Conﬁgure multi-factor authentication page, under Users can authenticate with these MFA types choose one of the following MFA types based on your business needs. For more information, see Available MFA types for IAM Identity Center. Conﬁgure MFA 203 AWS IAM Identity Center User Guide • Security keys and built-in authenticators • Authenticator apps 6. Choose Save changes. Conﬁgure MFA device enforcement Use the following procedure to determine whether your users must have a registered MFA device when signing in to the AWS access portal. For more information about MFA in IAM, see AWS Multi-factor authentication in IAM. To conﬁgure MFA device enforcement for your users 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Multi-factor authentication section, choose Conﬁgure. 5. On the Conﬁgure multi-factor authentication page, under If a user does not yet have a registered MFA device choose one of the following choices based on your business needs: • Require them to register an MFA device at sign in This is the default setting when you ﬁrst conﬁgure MFA for IAM Identity Center. Use this option when you want to require users who do not yet have a registered MFA device, to self-enroll a device during sign-in following a successful password authentication. This allows you to secure your organization’s AWS environments with MFA without having to individually enroll and distribute authentication devices to your users. During self- enrollment, your users can register any device from the available Available MFA types for IAM Identity Center you've previously enabled. After completing registration, users have the option to give their newly enrolled MFA device a friendly name, after which IAM Identity Center redirects the user
sso-ug-088	sso-ug.pdf	88	Center. Use this option when you want to require users who do not yet have a registered MFA device, to self-enroll a device during sign-in following a successful password authentication. This allows you to secure your organization’s AWS environments with MFA without having to individually enroll and distribute authentication devices to your users. During self- enrollment, your users can register any device from the available Available MFA types for IAM Identity Center you've previously enabled. After completing registration, users have the option to give their newly enrolled MFA device a friendly name, after which IAM Identity Center redirects the user to their original destination. If the user’s device is lost or stolen, you can simply remove that device from their account, and IAM Identity Center will require them to self-enroll a new device during their next sign-in. • Require them to provide a one-time password sent by email to sign in Use this option when you want to have veriﬁcation codes sent to users by email. Because email is not bound to a speciﬁc device, this option does not meet the bar for industry- Conﬁgure MFA 204 AWS IAM Identity Center User Guide standard multi-factor authentication. But it does improve security over having a password alone. Email veriﬁcation will only be requested if a user has not registered an MFA device. If the Context-aware authentication method has been enabled, the user will have the opportunity to mark the device on which they receive the email as trusted. Afterward they will not be required to verify an email code on future logins from that device, browser, and IP address combination. Note If you are using Active Directory as your IAM Identity Center enabled identity source, the email address will always be based on the Active Directory email attribute. Custom Active Directory attribute mappings will not override this behavior. • Block their sign-in Use the Block Their Sign-In option when you want to enforce MFA use by every user before they can sign in to AWS. Important If your authentication method is set to Context-aware a user might select the This is a trusted device check box on the sign-in page. In that case, that user will not be prompted for MFA even if you have the Block their sign in setting enabled. If you want these users to be prompted, change your authentication method to Always On. • Allow them to sign in Use this option to indicate that MFA devices are not required in order for your users to sign in to the AWS access portal. Users who chose to register MFA devices will still be prompted for MFA. 6. Choose Save changes. Allow users to register their own MFA devices IAM Identity Center administrators can allow users to self-register their own MFA devices. Conﬁgure MFA 205 AWS IAM Identity Center User Guide To allow users to register their own MFA devices 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Settings. 3. On the Settings page, choose the Authentication tab. 4. In the Multi-factor authentication section, choose Conﬁgure. 5. On the Conﬁgure multi-factor authentication page, under Who can manage MFA devices, choose Users can add and manage their own MFA devices. 6. Choose Save changes. Note After you set up self-registration for your users, you might want to send them a link to the procedure Registering your device for MFA. This topic provides instructions on how to set up their own MFA devices. Register an MFA device for users IAM Identity Center administrators can set up a new MFA device for access by a speciﬁc user in the IAM Identity Center console. Administrators must have physical access to the user's MFA device to register it. For example, if you conﬁgure MFA for a user who will use an MFA device running on a smartphone, you'll need physical access to the smartphone to complete the registration process. Alternatively, you can allow users to conﬁgure and manage their own MFA devices. For more information, see Allow users to register their own MFA devices. To register an MFA device 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Users. Choose a user in the list. Don't select the checkbox next to the user for this step. 3. On the user details page, choose the MFA devices tab, and then choose Register MFA device. 4. On the Register MFA device page, select one of the following MFA device types, and follow the instructions: • Authenticator app Register an MFA device 206 AWS IAM Identity Center User Guide 1. On the Set up the authenticator app page, IAM Identity Center displays conﬁguration information for the new MFA device, including a QR code graphic. The graphic is a representation of the secret key that is
sso-ug-089	sso-ug.pdf	89	in the list. Don't select the checkbox next to the user for this step. 3. On the user details page, choose the MFA devices tab, and then choose Register MFA device. 4. On the Register MFA device page, select one of the following MFA device types, and follow the instructions: • Authenticator app Register an MFA device 206 AWS IAM Identity Center User Guide 1. On the Set up the authenticator app page, IAM Identity Center displays conﬁguration information for the new MFA device, including a QR code graphic. The graphic is a representation of the secret key that is available for manual entry on devices that do not support QR codes. 2. Using the physical MFA device, do the following: a. Open a compatible MFA authenticator app. For a list of tested apps that you can use with MFA devices, see Virtual authenticator apps. If the MFA app supports multiple accounts (multiple MFA devices), choose the option to create a new account (a new MFA device). b. Determine whether the MFA app supports QR codes, and then do one of the following on the Set up the authenticator app page: i. Choose Show QR code, and then use the app to scan the QR code. For example, you might choose the camera icon or choose an option similar to Scan code. Then use the device's camera to scan the code. ii. Choose show secret key, and then type that secret key into your MFA app. Important When you conﬁgure an MFA device for IAM Identity Center, we recommend that you save a copy of the QR code or secret key in a secure place. This can help if the assigned user loses the phone or has to reinstall the MFA authenticator app. If either of those things happen, you can quickly reconﬁgure the app to use the same MFA conﬁguration. This avoids the need to create a new MFA device in IAM Identity Center for the user. 3. On the Set up the authenticator app page, under Authenticator code, type the one-time password that currently appears on the physical MFA device. Important Submit your request immediately after generating the code. If you generate the code and then wait too long to submit the request, the MFA device is successfully associated with the user. But the MFA device is out of sync. This happens because time-based one-time passwords (TOTP) expire after a short period of time. If this happens, you can resync the device. Register an MFA device 207 AWS IAM Identity Center User Guide 4. Choose Assign MFA. The MFA device can now start generating one-time passwords and is now ready for use with AWS. • Security key 1. On the Register your user's security key page, follow the instructions given to you by your browser or platform. Note The experience here varies based on the diﬀerent operating systems and browsers, so please follow the instructions displayed by your browser or platform. After your user's device has been successfully registered, you will be given the option to associate a friendly display name to your user's newly enrolled device. If you want to change this, choose Rename, enter the new name, and then choose Save. If you have enabled the option to allow users to manage their own devices, the user will see this friendly name in the AWS access portal. Renaming and deleting MFA devices in IAM Identity Center IAM Identity Center administrators can use the following procedures to rename or delete a user's MFA device. To rename an MFA device 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Users. Choose the user in the list. Don't select the checkbox next to the user for this step. 3. On the user details page, choose the MFA devices tab, select the device, and then choose Rename. 4. When prompted, enter the new name and then choose Rename. To delete an MFA device 1. Open the IAM Identity Center console. 2. In the left navigation pane, choose Users. Choose the user in the list. Rename and delete MFA devices 208 AWS IAM Identity Center User Guide 3. On the user details page, choose the MFA devices tab, select the device, and then choose Delete. 4. To conﬁrm, type DELETE, and then choose Delete. Rename and delete MFA devices 209 AWS IAM Identity Center User Guide Application access With AWS IAM Identity Center, you can control who can have single sign-on access to your applications. Users get seamless access to these applications after they use their directory credentials to sign in. IAM Identity Center securely communicates with these applications through a trusted relationship between IAM Identity Center and the application's service provider. This trust can be created in diﬀerent ways, depending on the application type. IAM
sso-ug-090	sso-ug.pdf	90	devices tab, select the device, and then choose Delete. 4. To conﬁrm, type DELETE, and then choose Delete. Rename and delete MFA devices 209 AWS IAM Identity Center User Guide Application access With AWS IAM Identity Center, you can control who can have single sign-on access to your applications. Users get seamless access to these applications after they use their directory credentials to sign in. IAM Identity Center securely communicates with these applications through a trusted relationship between IAM Identity Center and the application's service provider. This trust can be created in diﬀerent ways, depending on the application type. IAM Identity Center supports two application types: AWS managed applications and customer managed applications. AWS managed applications are conﬁgured directly from within the relevant application consoles or through the application APIs. Customer managed applications must be added to the IAM Identity Center console and conﬁgured with the appropriate metadata for both IAM Identity Center and the service provider. After you conﬁgure applications to work with IAM Identity Center, you can manage which users or groups access the applications. By default, no users are assigned to applications. You can also grant your employees access to the AWS Management Console for a speciﬁc AWS account in your organization. For more information, see AWS account access. Topics • AWS managed applications • Customer managed applications • Trusted identity propagation overview • Rotate IAM Identity Center certiﬁcates • Understand application properties in the IAM Identity Center console • Assign user access to applications in the IAM Identity Center console • Remove user access to SAML 2.0 applications • Map attributes in your application to IAM Identity Center attributes AWS managed applications AWS IAM Identity Center streamlines and simpliﬁes the task of connecting your workforce users to AWS managed applications such as Amazon Q Developer and Amazon QuickSight. With IAM AWS managed applications 210 AWS IAM Identity Center User Guide Identity Center, you can connect your existing identity provider once and synchronize users and groups from your directory, or create and manage your users directly in IAM Identity Center. By providing one point of federation, IAM Identity Center eliminates the need to set up federation or user and group synchronization for each application and reduces your administrative eﬀort. You also get a common view of user and group assignments. For a table of AWS applications that work with IAM Identity Center, see AWS managed applications that you can use with IAM Identity Center. Controlling access to AWS managed applications Access to AWS managed applications is controlled in two ways: • Initial entry to the application IAM Identity Center manages this through assignments to the application. By default, assignments are required for AWS managed applications. If you're an application administrator, you can choose whether to require assignments to an application. If assignments are required, when users sign in to the AWS access portal, only users who are assigned to the application directly or through a group assignment can view the application tile. If assignments aren't required, you can allow all IAM Identity Center users to enter the application. In this case, the application manages access to resources and the application tile is visible to all users who visit the AWS access portal. Important If you’re an IAM Identity Center administrator, you can use the IAM Identity Center console to remove assignments to AWS managed applications. Before you remove assignments, we recommend that you coordinate with the application administrator. You should also coordinate with the application administrator if you plan to modify the setting that determines whether assignments required, or automate application assignments. • Access to application resources The application manages this through independent resource assignments that it controls. Controlling access to applications 211 AWS IAM Identity Center User Guide AWS managed applications provide an administrative user interface that you can use to manage access to application resources. For example, QuickSight administrators can assign users to access dashboards based on their group membership. Most AWS managed applications also provide an AWS Management Console experience that enables you to assign users to the application. The console experience for these applications might integrate both functions, to combine user assignment capabilities with the ability to manage access to application resources. Sharing identity information Considerations for sharing identity information in AWS accounts IAM Identity Center supports most commonly used attributes across applications. These attributes include ﬁrst and last name, phone number, email address, address, and preferred language. Carefully consider which applications and which accounts can use this personally identiﬁable information. You can control access to this information in either of the following ways: • You can choose to enable access in only the AWS Organizations management account or in all accounts in AWS Organizations. • Alternatively, you can use service control policies (SCPs) to control which applications can access the information in
sso-ug-091	sso-ug.pdf	91	identity information Considerations for sharing identity information in AWS accounts IAM Identity Center supports most commonly used attributes across applications. These attributes include ﬁrst and last name, phone number, email address, address, and preferred language. Carefully consider which applications and which accounts can use this personally identiﬁable information. You can control access to this information in either of the following ways: • You can choose to enable access in only the AWS Organizations management account or in all accounts in AWS Organizations. • Alternatively, you can use service control policies (SCPs) to control which applications can access the information in which accounts in AWS Organizations. For example, if you enable access in the AWS Organizations management account only, then applications in member accounts have no access to the information. However, if you enable access in all accounts, you can use SCPs to disallow access by all applications except those you want to permit. Service control policies are a feature of AWS Organizations. For instructions on attaching an SCP, see Attaching and detaching service control policies in the AWS Organizations User Guide. Conﬁguring IAM Identity Center to share identity information IAM Identity Center provides an identity store that contains user and group attributes, excluding sign-in credentials. You can use either of the following methods to keep the users and groups in your IAM Identity Center identity store updated: • Use the IAM Identity Center identity store as your main identity source. If you choose this method, you manage your users, their sign-in credentials, and groups from within the IAM Sharing identity information 212 AWS IAM Identity Center User Guide Identity Center console or AWS Command Line Interface (AWS CLI). For more information, see Manage identities in IAM Identity Center. • Set up provisioning (synchronization) of users and groups coming from either of the following identity sources to your IAM Identity Center identity store: • Active Directory – For more information, see Connect to a Microsoft AD directory. • External identity provider – For more information, see Manage an external identity provider. If you choose this provisioning method, you continue managing your users and groups from within your identity source, and those changes are synchronized to the IAM Identity Center identity store. Whichever identity source you choose, IAM Identity Center can share the user and group information with AWS managed applications. That way, you can connect an identity source to IAM Identity Center once and then share identity information with multiple applications in the AWS Cloud. This eliminates the need to independently set up federation and identity provisioning with each application. This sharing feature also makes it easy to give your users access to many applications in diﬀerent AWS accounts. Constraining the use of AWS managed applications When you ﬁrst enable IAM Identity Center, it becomes available as an identity source for AWS managed applications across all accounts in your AWS Organizations. To constrain applications, you must implement service control policies (SCPs). SCPs are a feature of AWS Organizations that you can use to centrally control the maximum permissions that identities (users and roles) in your organization can have. You can use SCPs to block access to the IAM Identity Center user and group information and to prevent the application from being started, except in designated accounts. For more information, see Service control policies (SCPs) in the AWS Organizations User Guide. The following SCP example blocks access to the IAM Identity Center user and group information and prevents the application from being started, except in designated accounts (111111111111 and 222222222222): { "Sid": "DenyIdCExceptInDesignatedAWSAccounts", "Effect": "Deny", "Action": [ "identitystore:", "sso:", Constraining the use of AWS managed applications 213 User Guide AWS IAM Identity Center "sso-directory:", "sso-oauth:" ], "Resource": "*", "Condition": { "StringNotEquals": { "aws:PrincipalAccount": [ "111111111111", "222222222222" ] } } } AWS managed applications that you can use with IAM Identity Center IAM Identity Center lets you connect your existing identity source or create users once, enabling application owners to manage access to the following AWS managed applications without separate federation or user and group synchronization. AWS managed applications that integrate with IAM Identity Center AWS managed application Integrated with organization Integrated with account Enables trusted identity instance of IAM instances of IAM propagation Identity Center Identity Center through IAM Identity Center Amazon AppStream 2.0 Amazon Athena SQL Amazon CodeCatalyst Amazon Connect Yes Yes Yes Yes No Yes Yes No No Yes No No Applications that you can use with IAM Identity Center 214 AWS IAM Identity Center User Guide AWS managed application Amazon DataZone Amazon EMR on Amazon EC2 Amazon EMR Studio Amazon Kendra Amazon Managed Grafana Amazon Monitron Amazon OpenSearch Service Amazon OpenSearch Service Serverless Service OpenSearch user interface (Dashboards) Amazon Q Business Amazon Q Developer Integrated with organization Integrated with account Enables trusted identity instance of IAM instances of IAM
sso-ug-092	sso-ug.pdf	92	propagation Identity Center Identity Center through IAM Identity Center Amazon AppStream 2.0 Amazon Athena SQL Amazon CodeCatalyst Amazon Connect Yes Yes Yes Yes No Yes Yes No No Yes No No Applications that you can use with IAM Identity Center 214 AWS IAM Identity Center User Guide AWS managed application Amazon DataZone Amazon EMR on Amazon EC2 Amazon EMR Studio Amazon Kendra Amazon Managed Grafana Amazon Monitron Amazon OpenSearch Service Amazon OpenSearch Service Serverless Service OpenSearch user interface (Dashboards) Amazon Q Business Amazon Q Developer Integrated with organization Integrated with account Enables trusted identity instance of IAM instances of IAM propagation Identity Center Identity Center through IAM Identity Center Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No Yes Yes Yes Yes Yes* Yes Yes Yes No No No Yes Yes Yes No No Applications that you can use with IAM Identity Center 215 AWS IAM Identity Center User Guide AWS managed application Integrated with organization Integrated with account Enables trusted identity instance of IAM instances of IAM propagation Identity Center Identity Center through IAM Identity Center Amazon Q Developer operational investigations Amazon QuickSight Amazon Redshift Amazon S3 Access Grants Amazon SageMaker AI Studio Amazon WorkMail Amazon WorkSpaces Amazon WorkSpaces Secure Browser AWS App Studio AWS Client VPN AWS CLI Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes No Yes Yes No Yes No No No Yes Yes Yes No Yes No No No No No Applications that you can use with IAM Identity Center 216 AWS IAM Identity Center User Guide AWS managed application Integrated with organization Integrated with account Enables trusted identity instance of IAM instances of IAM propagation Identity Center Identity Center through IAM Identity Center AWS Deadline Cloud AWS IoT Events AWS IoT Fleet Hub AWS IoT SiteWise AWS Lake Formation AWS re:Post Private AWS Supply Chain AWS Systems Manager AWS Transfer Family web apps AWS Veriﬁed Access Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No Yes Yes Yes No Yes No No No No No Yes No No No Yes No Applications that you can use with IAM Identity Center 217 AWS IAM Identity Center User Guide * For Amazon Q Developer, account instances of IAM Identity Center are supported unless your users require access to the full set of Amazon Q Developer features on AWS websites. For more information, see Setting up Amazon Q Developer in the Amazon Q Developer User Guide. Quick start: Setting up IAM Identity Center to test AWS managed applications If your administrator hasn’t already provided you with access to IAM Identity Center, you can use the steps in this topic to set up IAM Identity Center to test AWS managed applications. You'll learn how to enable IAM Identity Center, create a user directly in IAM Identity Center, and assign that user to an AWS managed application. This topic provides quick-start steps on how to enable IAM Identity Center in either of the following ways: • With AWS Organizations – If you choose this option, an organization instance of IAM Identity Center is created. • Only in your speciﬁc AWS account – If you choose this option, an account instance of IAM Identity Center is created. For information about these instance types, see Organization and account instances of IAM Identity Center. Prerequisites Before you enable IAM Identity Center, conﬁrm the following: • You have an AWS account – If you don't, see Getting started with an AWS account in the AWS Account Management Reference Guide. • The AWS managed application works with IAM Identity Center – Review the list of AWS managed applications that you can use with IAM Identity Center to conﬁrm that the AWS managed application you want to test works with IAM Identity Center. • You’ve reviewed Regional considerations – Make sure that the AWS managed application you want to test is supported in the AWS Region where you enable IAM Identity Center. For more information, see the documentation for the AWS managed application. Setting up IAM Identity Center to test AWS managed applications 218 AWS IAM Identity Center Note User Guide You must deploy your AWS managed application in the same Region where you plan to enable IAM Identity Center. Setting up an organization instance of IAM Identity Center to test AWS managed applications Note This topic describes how to enable IAM Identity Center with AWS Organizations, which is the recommended way to enable IAM Identity Center. Conﬁrm your permissions To enable IAM Identity Center with AWS Organizations, you must sign in to the AWS Management Console as either of the following: • A user with administrative permissions in the AWS account where IAM Identity Center will be enabled with AWS Organizations. • The root
sso-ug-093	sso-ug.pdf	93	AWS managed application in the same Region where you plan to enable IAM Identity Center. Setting up an organization instance of IAM Identity Center to test AWS managed applications Note This topic describes how to enable IAM Identity Center with AWS Organizations, which is the recommended way to enable IAM Identity Center. Conﬁrm your permissions To enable IAM Identity Center with AWS Organizations, you must sign in to the AWS Management Console as either of the following: • A user with administrative permissions in the AWS account where IAM Identity Center will be enabled with AWS Organizations. • The root user (not recommended unless no other administrative users exist). Important The root user has access to all AWS services and resources in the account. As a security best practice, unless you have no other credentials, do not use your account's root credentials to access AWS resources. These credentials provide unrestricted account access and are diﬃcult to revoke. Step 1. Enable IAM Identity Center with AWS Organizations 1. Do one of the following to sign in to the AWS Management Console. • New to AWS (root user) – Sign in as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. Setting up IAM Identity Center to test AWS managed applications 219 AWS IAM Identity Center User Guide • Already using AWS with a standalone AWS account (IAM credentials) – Sign in using your IAM credentials with administrative permissions. 2. On the AWS Management Console Home page, select the IAM Identity Center service or navigate to the IAM Identity Center console. 3. Choose Enable, and enable IAM Identity Center with AWS Organizations. When you do this, you’re creating an organization instance of IAM Identity Center. Step 2. Create an administrative user in IAM Identity Center This procedure describes how to create a user directly in the built-in Identity Center directory. This directory isn't connected to any other directory that your administrator might use to manage workforce users. After you create the user in IAM Identity Center, you'll specify new credentials for this user. When you sign in as this user to test your AWS managed application, you'll sign in with the new credentials, not with any existing credentials that you use to access corporate resources. Note We recommend that you use this method for creating users for testing purposes only. 1. 2. 3. In the navigation pane of the IAM Identity Center console, choose Users, and then choose Add user. Follow the guidance in the console to add the user. Keep Send an email to this user with password setup instructions selected and make sure that you specify an email address to which you have access. In the navigation pane, choose AWS accounts, select the check box next to your account, and choose Assign users or groups. 4. Choose the Users tab, select the check box next to the user that you just added, and choose Next. 5. Choose Create permission set, and follow the guidance in the console to create the AdministratorAccess predeﬁned permission set. 6. When you’re done, the new permission set appears in the list. Close the Permission sets tab in your browser window, return to the Assign users and groups tab, and choose the refresh icon next to Create permission set. Setting up IAM Identity Center to test AWS managed applications 220 AWS IAM Identity Center User Guide 7. On the Assign users and groups browser tab, the new permission set appears in the list. Select the check box next to the name of the permission set, choose Next, and then choose Submit. 8. Sign out of the console. Step 3. Sign in to the AWS access portal as an administrative user The AWS access portal is a web portal that provides the user that you created with access to the AWS Management console. Before you can sign in to the AWS access portal, you must accept the invitation to join IAM Identity Center and activate your user credentials. 1. Check your email for the subject line Invitation to join AWS IAM Identity Center. 2. Choose Accept invitation, and follow the guidance on the sign-up page to set a new password, sign in, and register an MFA device for your user. 3. After you register your MFA device, the AWS access portal opens. 4. In the AWS access portal, select your AWS account and choose AdministratorAccess. You are redirected to the AWS Management Console. Step 4. Conﬁgure the AWS managed application to use IAM Identity Center 1. While you are signed in to the AWS Management Console, open the console for the AWS managed application that you plan to use. 2. Follow the guidance in the console to conﬁgure the AWS managed application to use IAM
sso-ug-094	sso-ug.pdf	94	to set a new password, sign in, and register an MFA device for your user. 3. After you register your MFA device, the AWS access portal opens. 4. In the AWS access portal, select your AWS account and choose AdministratorAccess. You are redirected to the AWS Management Console. Step 4. Conﬁgure the AWS managed application to use IAM Identity Center 1. While you are signed in to the AWS Management Console, open the console for the AWS managed application that you plan to use. 2. Follow the guidance in the console to conﬁgure the AWS managed application to use IAM Identity Center. During this process, you can assign the user that you created to the application. Setting up an account instance of IAM Identity Center to test AWS managed applications Note An account instance of IAM Identity Center limits your deployment to a single AWS account. You must enable this instance in the same AWS Region as the AWS application you want to test. Conﬁrm your app Setting up IAM Identity Center to test AWS managed applications 221 AWS IAM Identity Center User Guide All AWS managed applications that work with IAM Identity Center can be used with organization instances of IAM Identity Center. However, only some of these applications can be used with account instances of IAM Identity Center. Review the list of AWS managed applications that you can use with IAM Identity Center. Step1. Enable an account instance of IAM Identity Center 1. Do one of the following to sign in to the AWS Management Console. • New to AWS (root user) – Sign in as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. • Already using AWS with a standalone AWS account (IAM credentials) – Sign in using your IAM credentials with administrative permissions. 2. On the AWS Management Console Home page, select the IAM Identity Center service or navigate to the IAM Identity Center console. 3. Choose Enable. 4. On the Enable IAM Identity Center with AWS Organizations page, choose enable an account instance of IAM Identity Center. 5. On the Enable account instance of IAM Identity Center page, review the information and optionally add tags that you want to associate with this account instance. Then choose Enable. Step 2. Create a user in IAM Identity Center This procedure describes how to create a user directly in the built-in Identity Center directory. This directory isn't connected to any other directory that your administrator might use to manage workforce users. After you create the user in IAM Identity Center, you'll specify new credentials for this user. When you sign in as this user to test your AWS managed application, you'll sign in with the new credentials. The new credentials won't allow you to access other corporate resources. Note We recommend that you use this method for creating users for testing purposes only. 1. In the navigation pane of the IAM Identity Center console, choose Users, and then choose Add user. Setting up IAM Identity Center to test AWS managed applications 222 AWS IAM Identity Center User Guide 2. Follow the guidance in the console to add the user. Keep Send an email to this user with password setup instructions selected and make sure that you specify an email address to which you have access. 3. Sign out of the console. Step 3. Sign in to the AWS access portal as your IAM Identity Center user The AWS access portal is a web portal that provides the user that you created with access to the AWS Management console. Before you can sign in to the AWS access portal, you must accept the invitation to join IAM Identity Center and activate your user credentials. 1. Check your email for the subject line Invitation to join AWS IAM Identity Center. 2. Choose Accept invitation, and follow the guidance on the sign-up page to set a new password, sign in, and register an MFA device for your user. 3. After you register your MFA device, the AWS access portal opens. When applications are available to you, you’ll ﬁnd them under the Applications tab. Note AWS applications that support account instances allow users to sign in to applications without requiring additional permissions. Therefore, the Accounts tab will remain empty. Step 4. Conﬁgure the AWS managed application to use IAM Identity Center 1. While you are signed in to the AWS Management Console, open the console for the AWS managed application that you plan to use. 2. Follow the guidance in the console to conﬁgure the AWS managed application to use IAM Identity Center. During this process, you can assign the user that you created to the application. Viewing and changing details about an AWS managed application After you connect
sso-ug-095	sso-ug.pdf	95	account instances allow users to sign in to applications without requiring additional permissions. Therefore, the Accounts tab will remain empty. Step 4. Conﬁgure the AWS managed application to use IAM Identity Center 1. While you are signed in to the AWS Management Console, open the console for the AWS managed application that you plan to use. 2. Follow the guidance in the console to conﬁgure the AWS managed application to use IAM Identity Center. During this process, you can assign the user that you created to the application. Viewing and changing details about an AWS managed application After you connect an AWS managed application to IAM Identity Center by using the console or APIs for the application, the application is registered with IAM Identity Center. After an application is Viewing and changing application details 223 AWS IAM Identity Center User Guide registered with IAM Identity Center, you can view and change details about the application in the IAM Identity Center console. Information about the application includes whether user and group assignments are required, and if applicable, assigned users and groups and trusted applications for identity propagation. For information about trusted identity propagation, see Trusted identity propagation overview. To view and change information about an AWS managed application in the IAM Identity Center console 1. Open the IAM Identity Center console. 2. Choose Applications. 3. Choose the AWS managed tab. 4. Choose the link for the managed application you'd like to open and view. 5. If you want to change information about an AWS managed application, choose Action and then choose Edit Details. 6. You can change the application's display name, description, as well as the user and group assignment method. a. b. c. To change the display name, enter the desired name in the Display name ﬁeld and choose Save changes. To change the description, enter the desired description in the Description ﬁeld and choose Save changes. To change the user and group assignment method, make the desired change and choose Save changes. For more information, see the section called “Users, groups, and provisioning”. Disabling an AWS managed application To prevent users from authenticating to an AWS managed application, you can disable the application in the IAM Identity Center console. To disable an AWS managed application 1. Open the IAM Identity Center console. 2. Choose Applications. Disabling an AWS managed application 224 AWS IAM Identity Center User Guide 3. On the Applications page, under AWS managed applications, choose the application that you want to disable. 4. With the application selected, choose Actions, and then choose Disable. 5. 6. In the Disable application dialog box, choose Disable. In the AWS managed applications list, the application status appears as Inactive. Note If an AWS managed application is disabled, you can restore users abilty to authenticate to the application by choosing Actions and then Enable. Enabling identity-enhanced console sessions An identity-enhanced session for the console enhances a user's AWS console session by providing some additional user context to personalize that user's experience. This capability is currently supported for Amazon Q Developer Pro users of Amazon Q on AWS apps and websites. You can enable identity-enhanced console sessions without making any changes to existing access patterns or federation into the AWS console. If your users sign in to the AWS console with IAM (for example, if they sign in as IAM users or through federated access with IAM), they can continue using these methods. If your users sign in to the AWS access portal, they can continue using their IAM Identity Center user credentials. Topics • Prerequisites and considerations • How to enable identity-enhanced-console sessions • How identity-enhanced console sessions work Prerequisites and considerations Before you enable identity-enhanced console sessions, review the following prerequisites and considerations: • If your users access Amazon Q on AWS apps and websites through an Amazon Q Developer Pro subscription, you must enable identity-enhanced console sessions. Enabling identity-enhanced console sessions 225 AWS IAM Identity Center Note User Guide Amazon Q Developer users can access Amazon Q without identity-enhanced sessions, but they won't have access to their Amazon Q Developer Pro subscriptions. • Identity-enhanced console sessions require an organization instance of IAM Identity Center. • Integration with Amazon Q isn't supported if you enable IAM Identity Center in an opt-in AWS Region. • To enable identity-enhanced console sessions, you must have the following permissions: • sso:CreateApplication • sso:GetSharedSsoConfiguration • sso:ListApplications • sso:PutApplicationAssignmentConfiguration • sso:PutApplicationAuthenticationMethod • sso:PutApplicationGrant • sso:PutApplicationAccessScope • signin:CreateTrustedIdentityPropagationApplicationForConsole • signin:ListTrustedIdentityPropagationApplicationsForConsole • To enable your users to use identity-enhanced console sessions, you must grant them the sts:setContext permission in an identity-based policy. For information, see Granting users permissions to use identity-enhanced console sessions. How to enable identity-enhanced-console sessions You can enable identity-enhanced console sessions in the Amazon Q console or in the IAM Identity Center console. Enable identity-enhanced console
sso-ug-096	sso-ug.pdf	96	supported if you enable IAM Identity Center in an opt-in AWS Region. • To enable identity-enhanced console sessions, you must have the following permissions: • sso:CreateApplication • sso:GetSharedSsoConfiguration • sso:ListApplications • sso:PutApplicationAssignmentConfiguration • sso:PutApplicationAuthenticationMethod • sso:PutApplicationGrant • sso:PutApplicationAccessScope • signin:CreateTrustedIdentityPropagationApplicationForConsole • signin:ListTrustedIdentityPropagationApplicationsForConsole • To enable your users to use identity-enhanced console sessions, you must grant them the sts:setContext permission in an identity-based policy. For information, see Granting users permissions to use identity-enhanced console sessions. How to enable identity-enhanced-console sessions You can enable identity-enhanced console sessions in the Amazon Q console or in the IAM Identity Center console. Enable identity-enhanced console sessions in the Amazon Q console Before you enable identity-enhanced console sessions, you must have an organization instance of IAM Identity Center with an identity source connected. If you've already conﬁgured IAM Identity Center, skip to step 3. 1. Open the IAM Identity Center console. Choose Enable, and create an organization instance of IAM Identity Center. For information, see Enable IAM Identity Center. Enabling identity-enhanced console sessions 226 AWS IAM Identity Center User Guide 2. Connect your identity source to IAM Identity Center and provision users into IAM Identity Center. You can connect your existing identity source to IAM Identity Center or use the Identity Center directory if you're not already using another identity source. For more information, see IAM Identity Center identity source tutorials. 3. After you ﬁnish setting up IAM Identity Center, open the Amazon Q console and follow the steps in Subscriptions in the Amazon Q Developer User Guide. Make sure to enable identity- enhanced console sessions. Note If you don't have suﬃcient permissions to enable identity-enhanced console sessions, you might need to ask an IAM Identity Center administrator to perform this task for you in the IAM Identity Center console. For more information, see the next procedure. Enable identity-enhanced console sessions in the IAM Identity Center console If you're an IAM Identity Center administrator, you might be asked by another administrator to enable identity-enhanced console sessions in the IAM Identity Center console. 1. Open the IAM Identity Center console. 2. In the navigation pane, choose Settings. 3. Under Enable identity-enhanced sessions, choose Enable. 4. In the second message, choose Enable. 5. After you ﬁnish enabling identity-enhanced console sessions, a conﬁrmation message appears at the top of the Settings page. 6. In the Details section, the status for Identity-enhanced sessions is Enabled. How identity-enhanced console sessions work IAM Identity Center enhances a user's current console session to include the active IAM Identity Center user's ID and the IAM Identity Center session ID. Identity-enhanced console sessions include the following three values: • Identity store user ID (identitystore:UserId) - This value is used to uniquely identify a user in the identity source that is connected to IAM Identity Center. Enabling identity-enhanced console sessions 227 AWS IAM Identity Center User Guide • Identity store directory ARN (identitystore:IdentityStoreArn) - This value is the ARN of the identity store that is connected to IAM Identity Center, and where you can look up attributes for identitystore:UserId. • IAM Identity Center session ID - This value indicates whether the user's IAM Identity Center session is still valid. The values are the same, but obtained in diﬀerent ways and added at diﬀerent points of the process, depending on how the user signs in: • IAM Identity Center (AWS access portal): In this case, the user's identity store user ID and ARN values are already provided in the active IAM Identity Center session. IAM Identity Center enhances the current session by adding only the session ID. • Other sign-in methods: If the user signs in to AWS as an IAM user, with an IAM role, or as a federated user with IAM, none of these values are provided. IAM Identity Center enhances the current session by adding the identity store user ID, identity store directory ARN, and the session ID. Customer managed applications IAM Identity Center acts as a central identity service to your workforce users and groups. If you already use an identity provider (IdP), IAM Identity Center can integrate with your IdP so that you can provision your users and groups into IAM Identity Center and use your IdP for authentication. With a single connection, IAM Identity Center represents your IdP in front of multiple AWS services and enables your OAuth 2.0 applications to request access to data in these services on behalf of your users. You can also use IAM Identity Center to assign your users access to SAML 2.0 applications. • If your application supports JSON Web Tokens (JWTs), you can use the trusted identity propagation feature of IAM Identity Center to enable your application to request access to data in AWS services on behalf of your users. Trusted identity propagation is built on the OAuth 2.0 Authorization Framework and includes an
sso-ug-097	sso-ug.pdf	97	connection, IAM Identity Center represents your IdP in front of multiple AWS services and enables your OAuth 2.0 applications to request access to data in these services on behalf of your users. You can also use IAM Identity Center to assign your users access to SAML 2.0 applications. • If your application supports JSON Web Tokens (JWTs), you can use the trusted identity propagation feature of IAM Identity Center to enable your application to request access to data in AWS services on behalf of your users. Trusted identity propagation is built on the OAuth 2.0 Authorization Framework and includes an option for applications to exchange identity tokens that come from an external OAuth 2.0 authorization server for tokens issued by IAM Identity Center and recognized by AWS services. For more information, see Trusted identity propagation use cases. • If your application supports SAML 2.0, you can connect it to an organization instance of IAM Identity Center. You can use IAM Identity Center to assign access to your SAML 2.0 application. Customer managed applications 228 AWS IAM Identity Center Topics • Single sign-on access to SAML 2.0 and OAuth 2.0 applications • Setting up customer managed SAML 2.0 applications User Guide Single sign-on access to SAML 2.0 and OAuth 2.0 applications IAM Identity Center enables you to provide your users with single sign-on access to SAML 2.0 or OAuth 2.0 applications. The following topics provide a high-level overview of SAML 2.0 and OAuth 2.0. Topics • SAML 2.0 • OAuth 2.0 SAML 2.0 SAML 2.0 is an industry standard used for securely exchanging SAML assertions that pass information about a user between a SAML authority (called an identity provider or IdP), and a SAML 2.0 consumer (called a service provider or SP). IAM Identity Center uses this information to provide federated single sign-on access for those users who are authorized to use applications within the AWS access portal. OAuth 2.0 OAuth 2.0 is a protocol that allows applications to access and share user data securely without sharing passwords. This capability provides a secure and standardized way for users to allow applications access to their resources. Access is facilitated by diﬀerent OAuth 2.0 grant ﬂows. IAM Identity Center enables applications that run on public clients to retrieve temporary credentials to access AWS accounts and services programmatically on behalf of their users. Public clients are typically desktops, laptops, or other mobile devices that are used to run applications locally. Examples of AWS applications that run on public clients include the AWS Command Line Interface (AWS CLI), AWS Toolkit, and AWS Software Development Kits (SDKs). To enable these applications to obtain credentials, IAM Identity Center supports portions of the following OAuth 2.0 ﬂows: • Authorization Code Grant with Proof Key for Code Exchange (PKCE) (RFC 6749 and RFC 7636) SAML 2.0 and OAuth 2.0 applications 229 AWS IAM Identity Center User Guide • Device Authorization Grant (RFC 8628) Note These grant types can be used only with AWS services that support this capability. These services may not support this grant type in all AWS Regions. Refer to the documentation of relevant AWS services for regional diﬀerences. OpenID Connect (OIDC) is an authentication protocol that is based on the OAuth 2.0 Framework. OIDC speciﬁes how to use OAuth 2.0 for authentication. Through the IAM Identity Center OIDC service APIs, an application registers an OAuth 2.0 client and uses one of these ﬂows to obtain an access token that provides permissions to IAM Identity Center protected APIs. An application speciﬁes access scopes to declare its intended API user. After you, as the IAM Identity Center administrator, conﬁgure your identity source, your application end users must complete a sign- in process, if they have not already done so. Your end users must then provide their consent to allow the application to make API calls. These API calls are made using the users' permissions. In response, IAM Identity Center returns an access token to the application that contains the access scopes to which the users consented. Using an OAuth 2.0 grant ﬂow OAuth 2.0 grant ﬂows are only available through AWS managed applications that support the ﬂows. To use an OAuth 2.0 ﬂow, your instance of IAM Identity Center and any supported AWS managed applications that you use must be deployed in a single AWS Region. Refer to the documentation for each AWS service to determine the regional availability of AWS managed applications and the instance of IAM Identity Center that you want to use. To use an application that uses an OAuth 2.0 ﬂow, the end user must enter the URL where the application will connect and register with your instance of IAM Identity Center. Depending on the application, as the administrator, you must provide your users with the AWS access portal URL or the Issuer URL
sso-ug-098	sso-ug.pdf	98	Center and any supported AWS managed applications that you use must be deployed in a single AWS Region. Refer to the documentation for each AWS service to determine the regional availability of AWS managed applications and the instance of IAM Identity Center that you want to use. To use an application that uses an OAuth 2.0 ﬂow, the end user must enter the URL where the application will connect and register with your instance of IAM Identity Center. Depending on the application, as the administrator, you must provide your users with the AWS access portal URL or the Issuer URL of your instance of IAM Identity Center. You can ﬁnd these two settings on the IAM Identity Center console Settings page. For additional information about conﬁguring a client application, refer to that application’s documentation. The end user experience for signing into an application and providing consent depends on whether the application uses the Authorization Code Grant with PKCE or Device Authorization Grant. SAML 2.0 and OAuth 2.0 applications 230 AWS IAM Identity Center User Guide Authorization Code Grant with PKCE This ﬂow is used by applications that run on a device that has a browser. 1. A browser window opens. 2. If the user has not authenticated, the browser redirects them to complete user authentication. 3. After authentication, the user is presented with a consent screen that displays the following information: • The name of the application • The access scopes that the application is requesting consent to use 4. The user can cancel the consent process or they can give their consent and the application proceeds with access based on the user’s permissions. Device Authorization Grant This ﬂow can be used by applications that run on a device with or without a browser. When the application initiates the ﬂow, the application presents a URL and a user code that the user must verify later in the ﬂow. The user code is necessary because the application that initiates the ﬂow might be running on a diﬀerent device than the device on which the user provides consent. The code ensures that the user is consenting to the ﬂow they initiated on the other device. Note If you have clients using device.sso.region.amazonaws.com, you must update your authorization ﬂow to use Proof Key for Code Exchange (PKCE). For more information, see Conﬁguring IAM Identity Center authentication with the AWS CLI in the AWS Command Line Interface User Guide. 1. When the ﬂow initiates from a device with a browser, a browser window opens. When the ﬂow initiates from a device without a browser, the user must open a browser on a diﬀerent device and go to the URL that the application presented. 2. In either case, if the user has not authenticated, the browser redirects them to complete user authentication. 3. After authentication, the user is presented with a consent screen that displays the following information: SAML 2.0 and OAuth 2.0 applications 231 AWS IAM Identity Center User Guide • The name of the application • The access scopes that the application is requesting consent to use • The user code that the application presented to the user 4. The user can cancel the consent process or they can give their consent and the application proceeds with access based on the user’s permissions. Access scopes A scope deﬁnes the access for a service that can be accessed through an OAuth 2.0 ﬂow. Scopes are a way for the service, also called a resource server, to group permissions related to actions and the service resources, and they specify the coarse-grained operations that OAuth 2.0 clients can request. When an OAuth 2.0 client registers with the IAM Identity Center OIDC service, the client speciﬁes the scopes to declare its intended actions, for which the user must provide consent. OAuth 2.0 clients use scope values as deﬁned in section 3.3 of OAuth 2.0 (RFC 6749) to specify what permissions are being requested for an access token. Clients can specify a maximum of 25 scopes when requesting an access token. When a user provides consent during an Authorization Code Grant with PKCE or Device Authorization Grant ﬂow, IAM Identity Center encodes the scopes into the access token it returns. AWS adds scopes to IAM Identity Center for supported AWS services. The following table lists the scopes that the IAM Identity Center OIDC service supports when you register a public client. Access scopes supported by the IAM Identity Center OIDC service when registering a public client Scope Description sso:accou nt:access Access IAM Identity Center managed accounts and permission sets. Services supported by IAM Identity Center codewhisp erer:analysis Enable access to Amazon Q Developer code analysis. AWS Builder ID and IAM Identity Center codewhisp erer:comp letions Enable access to Amazon Q inline code suggestions. AWS Builder ID and IAM
sso-ug-099	sso-ug.pdf	99	it returns. AWS adds scopes to IAM Identity Center for supported AWS services. The following table lists the scopes that the IAM Identity Center OIDC service supports when you register a public client. Access scopes supported by the IAM Identity Center OIDC service when registering a public client Scope Description sso:accou nt:access Access IAM Identity Center managed accounts and permission sets. Services supported by IAM Identity Center codewhisp erer:analysis Enable access to Amazon Q Developer code analysis. AWS Builder ID and IAM Identity Center codewhisp erer:comp letions Enable access to Amazon Q inline code suggestions. AWS Builder ID and IAM Identity Center SAML 2.0 and OAuth 2.0 applications 232 codewhisp erer:conv ersations codewhisp erer:task assist codewhisp erer:tran sformations AWS IAM Identity Center User Guide Scope Description Enable access to Amazon Q chat. Services supported by AWS Builder ID and IAM Identity Center Enable access to Amazon Q Developer Agent for software development. AWS Builder ID and IAM Identity Center Enable access to Amazon Q Developer Agent for code transformation. AWS Builder ID and IAM Identity Center codecatal yst:read_write Read and write to your Amazon CodeCatalyst resources, allowing access to all your existing AWS Builder ID and IAM Identity Center resources. Setting up customer managed SAML 2.0 applications If you use customer managed applications that support SAML 2.0, you can federate your IdP to IAM Identity Center through SAML 2.0 and use IAM Identity Center to manage user access to those applications. You can select a SAML 2.0 application from a catalog of commonly used applications in the IAM Identity Center console, or you can set up your own SAML 2.0 application. Note If you have customer managed applications that support OAuth 2.0 and your users need access from these applications to AWS services, you can use trusted identity propagation. With trusted identity propagation, a user can sign in to an application, and that application can pass the users’ identity in requests to access data in AWS services. Topics • Set up an application from the IAM Identity Center application catalog • Set up your own SAML 2.0 application SAML 2.0 application setup 233 AWS IAM Identity Center User Guide Set up an application from the IAM Identity Center application catalog You can use the application catalog in the IAM Identity Center console to add many commonly used SAML 2.0 applications that work with IAM Identity Center. Examples include Salesforce, Box, and Microsoft 365. Most applications provide detailed information about how to set up the trust between IAM Identity Center and the application's service provider. This information is available in the conﬁguration page for the application, after you select the application in the catalog. After you conﬁgure the application, you can assign access to users or groups in IAM Identity Center as needed. Use this procedure to set up a SAML 2.0 trust relationship between IAM Identity Center and your application's service provider. Before you begin this procedure, it's helpful to have the service provider's metadata exchange ﬁle so that you can more eﬃciently set up the trust. If you don't have this ﬁle, you can still use this procedure to conﬁgure the trust it manually. To add and conﬁgure an application from the application catalog 1. Open the IAM Identity Center console. 2. Choose Applications. 3. Choose the Customer managed tab. 4. Choose Add application. 5. On the Select application type page, under Setup preference, choose I want to select an application from the catalog. 6. Under Application catalog, start typing the name of the application that you want to add in the search box. 7. Choose the name of the application from the list when it appears in the search results, and then choose Next. 8. On the Conﬁgure application page, the Display name and Description ﬁelds are prepopulated with relevant details for the application. You can edit this information. 9. Under IAM Identity Center metadata, do the following: a. Under IAM Identity Center SAML metadata ﬁle, choose Download to download the identity provider metadata. SAML 2.0 application setup 234 AWS IAM Identity Center User Guide b. Under IAM Identity Center certiﬁcate, choose Download certiﬁcate to download the identity provider certiﬁcate. Note You will need these ﬁles later when you set up the application from the service provider's website. Follow the instructions from that provider. 10. (Optional) Under Application properties, you can specify the Application start URL, Relay state, and Session duration. For more information, see Understand application properties in the IAM Identity Center console. 11. Under Application metadata, do one of the following: a. b. If you have a metadata ﬁle, choose Upload application SAML metadata ﬁle. Then, select Choose ﬁle to ﬁnd and select the metadata ﬁle. If you don't have a metadata ﬁle, choose Manually type your metadata values, and then provide the Application ACS URL
sso-ug-100	sso-ug.pdf	100	you set up the application from the service provider's website. Follow the instructions from that provider. 10. (Optional) Under Application properties, you can specify the Application start URL, Relay state, and Session duration. For more information, see Understand application properties in the IAM Identity Center console. 11. Under Application metadata, do one of the following: a. b. If you have a metadata ﬁle, choose Upload application SAML metadata ﬁle. Then, select Choose ﬁle to ﬁnd and select the metadata ﬁle. If you don't have a metadata ﬁle, choose Manually type your metadata values, and then provide the Application ACS URL and Application SAML audience values. 12. Choose Submit. You're taken to the details page of the application that you just added. Set up your own SAML 2.0 application You can set up your own applications that allow identity federation using SAML 2.0 and add them to IAM Identity Center. Most of the steps for setting up your own SAML 2.0 applications are the same as setting up a SAML 2.0 application from the application catalog in the IAM Identity Center console. However, you must also provide additional SAML attribute mappings for your own SAML 2.0 applications. These mappings enable IAM Identity Center to populate the SAML 2.0 assertion correctly for your application. You can provide this additional SAML attribute mapping when you set up the application for the ﬁrst time. You can also provide SAML 2.0 attribute mappings on the application details page in the IAM Identity Center console. Use the following procedure to set up a SAML 2.0 trust relationship between IAM Identity Center and your SAML 2.0 application's service provider. Before you begin this procedure, make sure that you have the service provider's certiﬁcate and metadata exchange ﬁles so that you can ﬁnish setting up the trust. SAML 2.0 application setup 235 AWS IAM Identity Center User Guide To set up your own SAML 2.0 application 1. Open the IAM Identity Center console. 2. Choose Applications. 3. Choose the Customer managed tab. 4. Choose Add application. 5. On the Select application type page, under Setup preference, choose I have an application I want to set up. 6. Under Application type, choose SAML 2.0. 7. Choose Next. 8. On the Conﬁgure application page, under Conﬁgure application, enter a Display name for the application, such as MyApp. Then, enter a Description. 9. Under IAM Identity Center metadata, do the following: a. Under IAM Identity Center SAML metadata ﬁle, choose Download to download the identity provider metadata. b. Under IAM Identity Center certiﬁcate, choose Download to download the identity provider certiﬁcate. Note You will need these ﬁles later when you set up the custom application from the service provider's website. 10. (Optional) Under Application properties, you can also specify the Application start URL, Relay state, and Session duration. For more information, see Understand application properties in the IAM Identity Center console. 11. Under Application metadata, choose Manually type your metadata values. Then, provide the Application ACS URL and Application SAML audience values. 12. Choose Submit. You're taken to the details page of the application that you just added. SAML 2.0 application setup 236 AWS IAM Identity Center User Guide Trusted identity propagation overview Trusted identity propagation is a feature of IAM Identity Center that enables administrators of AWS services to grant permissions based on user attributes such as group associations. With trusted identity propagation, identity context is added to an IAM role to identify the user requesting access to AWS resources. This context is propagated to other AWS services. Identity context comprises information that AWS services use to make authorization decisions when they receive access requests. This information includes metadata that identiﬁes the requester (for example, an IAM Identity Center user), the AWS service to which access is requested (for example, Amazon Redshift), and the scope of access (for example, read only access). The receiving AWS service uses this context, and any permissions assigned to the user, to authorize access to its resources. Beneﬁts of trusted identity propagation Trusted identity propagation allows the administrators of AWS services to grant permissions to resources, such as data, using the corporate identities of your workforce. In addition, they can audit who accessed what data by looking at service logs or AWS CloudTrail. If you're an IAM Identity Center administrator, you may be asked by other AWS service administrators to enable trusted identity propagation. Enabling trusted identity propagation The process of enabling trusted identity propagation involves the following two steps: 1. Enable IAM Identity Center and connect your existing source of identities to IAM Identity Center - You'll continue to manage your workforce identities in your existing source of identities; connecting it to IAM Identity Center creates a reference to your workforce that all AWS services in your use case can share. It's also available
sso-ug-101	sso-ug.pdf	101	by looking at service logs or AWS CloudTrail. If you're an IAM Identity Center administrator, you may be asked by other AWS service administrators to enable trusted identity propagation. Enabling trusted identity propagation The process of enabling trusted identity propagation involves the following two steps: 1. Enable IAM Identity Center and connect your existing source of identities to IAM Identity Center - You'll continue to manage your workforce identities in your existing source of identities; connecting it to IAM Identity Center creates a reference to your workforce that all AWS services in your use case can share. It's also available for data owners to use in future use cases. 2. Connect the AWS services in your use case to IAM Identity Center - The administrator of each AWS service in the trusted identity propagation use case follows the guidance in the respective service documentation to connect the service to IAM Identity Center. Trusted identity propagation 237 AWS IAM Identity Center Note User Guide If your use case involves a third-party or customer developed application, you enable trusted identity propagation by conﬁguring a trust relationship between the identity provider that authenticates the application users and IAM Identity Center. This allows your application to take advantage of the trusted identity propagation ﬂow previously described. For more information, see Using applications with a trusted token issuer. How trusted identity propagation works The following diagram shows the high-level workﬂow for trusted identity propagation: 1. Users authenticate with a client-facing application, for example QuickSight. 2. The client-facing application requests access to use an AWS service to query data and includes information on the user. Note Some trusted identity propagation use cases involve tools that interact with AWS services using service drivers. You can ﬁnd out if this applies to your use case in the use case guidance. 3. The AWS service veriﬁes the user identity with IAM Identity Center and compares the user attributes, like their group associations, with those required for access. The AWS service authorizes the access so long as the user or their group has the necessary permissions. 4. AWS services may log the user identiﬁer in AWS CloudTrail and in their service logs. Check the service documentation for details. The following image provides an overview of the previously described steps in the trusted identity propagation workﬂow: How trusted identity propagation works 238 AWS IAM Identity Center User Guide Topics • Prerequisites and considerations • Trusted identity propagation use cases • Using trusted identity propagation with customer managed applications Prerequisites and considerations Before you set up trusted identity propagation, review the following prerequisites and considerations. Topics • Prerequisites • Considerations • Considerations for customer managed applications Prerequisites To use trusted identity propagation, ensure your environment meets the following prerequisites: • Enable and provision IAM Identity Center • To use trusted identity propagation, you must enable IAM Identity Center in the same AWS Region where the AWS applications and services your users will access are enabled. For information, see Enable IAM Identity Center. Prerequisites and considerations 239 AWS IAM Identity Center User Guide • IAM Identity Center Organization instance is recommended - We recommend you use an organization instance of IAM Identity Center that you enable in the management account of AWS Organizations. You can delegate administration of an organization instance of IAM Identity Center to a member account. If you choose an account instance of IAM Identity Center, all AWS services that you want users to access with trusted identity propagation must reside in the same AWS account where you enable IAM Identity Center. For more information, see Account instances of IAM Identity Center. • Connect your existing identity provider to IAM Identity Center and provision your users and groups into IAM Identity Center. For more information, see IAM Identity Center identity source tutorials. • Connect the AWS managed applications and services in your trusted identity propagation use case to IAM Identity Center. To use trusted identity propagation, AWS managed applications must be connected to IAM Identity Center. Considerations Keep in mind the following considerations when conﬁguring and using trusted identity propagation: • Organization vs account instance of IAM Identity Center • An organization instance of IAM Identity Center will give you the most control and ﬂexibility to grow your use cases to multiple AWS accounts, users, and AWS services. If you are unable to use an organization instance, your use case may be supported with account instances of IAM Identity Center. To learn more about which AWS services in your use case support account instances of IAM Identity Center, see AWS managed applications that you can use with IAM Identity Center. • Multi-account permissions (permission sets) not required • Trusted identity propagation doesn't require you to set up multi-account permissions (permission sets). You can enable IAM Identity Center and use it
sso-ug-102	sso-ug.pdf	102	the most control and ﬂexibility to grow your use cases to multiple AWS accounts, users, and AWS services. If you are unable to use an organization instance, your use case may be supported with account instances of IAM Identity Center. To learn more about which AWS services in your use case support account instances of IAM Identity Center, see AWS managed applications that you can use with IAM Identity Center. • Multi-account permissions (permission sets) not required • Trusted identity propagation doesn't require you to set up multi-account permissions (permission sets). You can enable IAM Identity Center and use it for trusted identity propagation only. Considerations for customer managed applications Your workforce can beneﬁt from trusted identity propagation even if your users interact with client-facing applications that are not managed by AWS, for example Tableau or your custom- developed applications. The users of these applications may not be provisioned in IAM Identity Prerequisites and considerations 240 AWS IAM Identity Center User Guide Center. To enable the smooth recognition and authorization of user access to AWS resources, IAM Identity Center enables you to conﬁgure a trusted relationship between the identity provider authenticating your users and IAM Identity Center. For more information, see Using applications with a trusted token issuer. In addition, conﬁguring trusted identity propagation for your application will require: • Your application must use OAuth 2.0 framework for authentication. Trusted identity propagation does not support SAML 2.0 integrations. • Your application must be recognized by IAM Identity Center. Follow the guidance speciﬁc to your use case. Trusted identity propagation use cases As an IAM Identity Center administrator, you might be asked to help conﬁgure trusted identity propagation from user facing applications to AWS services. To support this request, you'll need the following information: • What client-facing application will your users interface with? • Which AWS services are used to query the data and to authorize access to the data? • Which AWS service authorizes access to the data? Your role in enabling trusted identity propagation use cases that don't involve third-party applications or custom-developed applications is to: 1. Enable IAM Identity Center. 2. Connect your existing source of identities to IAM Identity Center. The remaining steps of the trusted identity conﬁguration for these use cases are performed within the connected AWS services and applications. The administrators of the connected AWS services or applications should refer to the respective user guides for comprehensive service-speciﬁc guidance. Your role in enabling trusted identity propagation use cases that involve third-party applications or custom-developed applications includes the steps of Enable IAM Identity Center and connecting your source of identities as well as: Use cases 241 AWS IAM Identity Center User Guide 1. Conﬁguring the connection of your identity provider (IdP) to the third-party party or custom- developed application. 2. Enabling IAM Identity Center to recognize the third-party or custom-developed application. 3. Conﬁguring your IdP as a trusted token issuer in IAM Identity Center. For more information, see Using applications with a trusted token issuer. The administrators of the connected applications and AWS services should refer to the respective user guides for comprehensive service-speciﬁc guidance. Analytics and data lakehouse use cases You can enable trusted propagation use cases with the following analytics services: • Amazon Redshift - For guidance, see Trusted identity propagation with Amazon Redshift. • Amazon EMR - For guidance, see Trusted identity propagation with Amazon EMR. • Amazon Athena - For guidance, see Trusted identity propagation with Amazon Athena. Additional use cases You can enable IAM Identity Center and trusted identity propagation with these additional AWS services: • Amazon Q Business - for guidance, see: • Admin workﬂow for apps using IAM Identity Center. • Conﬁguring an Amazon Q Business application using IAM Identity Center. • Conﬁgure Amazon Q Business with IAM Identity Center trusted identity propagation. • Amazon OpenSearch Service - for guidance, see: • IAM Identity Center Trusted Identity Propagation Support for Amazon OpenSearch Service. • Centralized OpenSearch user interface (Dashboards) with Amazon OpenSearch Service. • AWS Transfer Family - for guidance, see: • Transfer Family web apps. Topics • Trusted identity propagation with Amazon Redshift Use cases 242 AWS IAM Identity Center User Guide • Trusted identity propagation with Amazon EMR • Trusted identity propagation with Amazon Athena • Authorization services Trusted identity propagation with Amazon Redshift The steps to enable trusted identity propagation depend on whether your users interact with AWS managed applications or customer managed applications. The following diagram shows a trusted identity propagation conﬁguration for client-facing applications - either AWS managed or external to AWS - that query Amazon Redshift data with access control provided either by Amazon Redshift or by authorization services, such as AWS Lake Formation or Amazon S3 Access Grants. When trusted identity propagation to Amazon Redshift is enabled, Redshift administrators can conﬁgure Redshift
sso-ug-103	sso-ug.pdf	103	EMR • Trusted identity propagation with Amazon Athena • Authorization services Trusted identity propagation with Amazon Redshift The steps to enable trusted identity propagation depend on whether your users interact with AWS managed applications or customer managed applications. The following diagram shows a trusted identity propagation conﬁguration for client-facing applications - either AWS managed or external to AWS - that query Amazon Redshift data with access control provided either by Amazon Redshift or by authorization services, such as AWS Lake Formation or Amazon S3 Access Grants. When trusted identity propagation to Amazon Redshift is enabled, Redshift administrators can conﬁgure Redshift to automatically create roles for IAM Identity Center as the identity provider, map Redshift roles to groups in IAM Identity Center, and use Redshift role-based access control to grant access. Supported client-facing applications AWS managed applications Use cases 243 AWS IAM Identity Center User Guide The following AWS managed client-facing applications support trusted identity propagation to Amazon Redshift: • Amazon Redshift Query Editor V2 • QuickSight Note If you're using Amazon Redshift Spectrum to access external databases or tables in AWS Glue Data Catalog, consider setting up Lake Formation and Amazon S3 Access Grants to provide ﬁne-grain access control. Customer managed applications The following customer managed applications support trusted identity propagation to Amazon Redshift: • Tableau including Tableau Desktop, Tableau Server, and Tableau Prep • To enable trusted identity propagation for users of Tableau, refer to Integrate Tableau and Okta with Amazon Redshift using IAM Identity Center in the AWS Big Data Blog. • SQL Clients (DBeaver and DBVisualizer) • To enable trusted identity propagation for users of SQL Clients (DBeaver and DBVisualizer), refer to Integrate Identity Provider (IdP) with Amazon Redshift Query Editor V2 and SQL Client using IAM Identity Center for seamless Single Sign-On in the AWS Big Data Blog. Setting up trusted identity propagation with Amazon Redshift Query Editor V2 The following procedure walks you through how to achieve trusted identity propagation from Amazon Redshift Query Editor V2 to Amazon Redshift. Prerequisites Before you can get started with this tutorial, you'll need to set up the following: 1. Enable IAM Identity Center. Organization instance is recommended. For more information, see Prerequisites and considerations. 2. Provision the users and groups from your source of identities into IAM Identity Center. Use cases 244 AWS IAM Identity Center User Guide Enabling trusted identity propagation includes tasks performed by an IAM Identity Center administrator in the IAM Identity Center console and tasks performed by an Amazon Redshift administrator in the Amazon Redshift console. Tasks performed by the IAM Identity Center administrator The following tasks needed to be complete by the IAM Identity Center administrator: 1. Create an IAM role in the account where the Amazon Redshift cluster or Serverless instance exists with the following permission policy. For more information, see IAM Role creation. • The following policy examples includes the necessary permissions to complete this tutorial. To use this policy, replace the italicized placeholder text in the example policy with your own information. For additional directions, see Create a policy or Edit a policy. Permission policy: { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowRedshiftApplication", "Effect": "Allow", "Action": [ "redshift:DescribeQev2IdcApplications", "redshift-serverless:ListNamespaces", "redshift-serverless:ListWorkgroups", "redshift-serverless:GetWorkgroup" ], "Resource": "" }, { "Sid": "AllowIDCPermissions", "Effect": "Allow", "Action": [ "sso:DescribeApplication", "sso:DescribeInstance" ], "Resource": [ "arn:aws:sso:::instance/Your-IAM-Identity-Center-Instance ID", "arn:aws:sso::Your-AWS-Account-ID:application/Your-IAM- Identity-Center-Instance-ID/" Use cases 245 AWS IAM Identity Center User Guide ] } ] } Trust policy: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "redshift-serverless.amazonaws.com", "redshift.amazonaws.com" ] }, "Action": [ "sts:AssumeRole", "sts:SetContext" ] } ] } 2. Create a permission set in the AWS Organizations management account where IAM Identity Center is enabled. You’ll use it in the next step to allow federated users to access Redshift Query Editor V2. a. Go to the IAM Identity Center console, under Multi-Account permissions, choose Permission sets. b. Choose Create permission set. c. Choose Custom permission set and then choose Next. d. Under AWS managed policies, choose AmazonRedshiftQueryEditorV2ReadSharing. e. Under Inline policy, add the following policy: { "Version": "2012-10-17", "Statement": [ Use cases 246 AWS IAM Identity Center { User Guide "Sid": "Statement1", "Effect": "Allow", "Action": [ "redshift:DescribeQev2IdcApplications", "redshift-serverless:ListNamespaces", "redshift-serverless:ListWorkgroups", "redshift-serverless:GetWorkgroup" ], "Resource": "*" } ] } f. Select Next and then provide a name for the permission set name. For example, Redshift-Query-Editor-V2. g. Under Relay state – optional, set default relay state to the Query Editor V2 URL, using the format: https://your-region.console.aws.amazon.com/sqlworkbench/home. h. Review the settings and choose Create. i. Navigate to the IAM Identity Center Dashboard and copy the AWS access portal URL from the Setting Summary section. j. Open a new Incognito Browser Window and paste the URL. This will take you to your AWS access portal, ensuring you are signing in with an IAM Identity Center user. Use cases 247 AWS IAM Identity Center User
sso-ug-104	sso-ug.pdf	104	Next and then provide a name for the permission set name. For example, Redshift-Query-Editor-V2. g. Under Relay state – optional, set default relay state to the Query Editor V2 URL, using the format: https://your-region.console.aws.amazon.com/sqlworkbench/home. h. Review the settings and choose Create. i. Navigate to the IAM Identity Center Dashboard and copy the AWS access portal URL from the Setting Summary section. j. Open a new Incognito Browser Window and paste the URL. This will take you to your AWS access portal, ensuring you are signing in with an IAM Identity Center user. Use cases 247 AWS IAM Identity Center User Guide For more information about permission set, see Manage AWS accounts with permission sets. 3. Enable federated users access to Redshift Query Editor V2. a. b. In the AWS Organizations management account, open the IAM Identity Center console. In the navigation pane, under Multi-account permissions, choose AWS accounts. c. On the AWS accounts page, select the AWS account that you want to assign access to. d. Choose Assign users or groups. e. On the Assign users and groups page, choose the users and or groups that you want to create the permission set for. Then, choose Next. f. On the Assign permission sets page, choose the permission set you created in the previous step. Then, choose Next. g. On the Review and submit assignments page, review your selections and choose Submit. Tasks performed by an Amazon Redshift administrator Enabling trusted identity propagation to Amazon Redshift requires an Amazon Redshift cluster administrator or Amazon Redshift Serverless administrator to perform a number of tasks in the Amazon Redshift console. For more information, see Integrate Identity Provider (IdP) with Amazon Redshift Query Editor V2 and SQL Client using IAM Identity Center for seamless Single Sign-On in the AWS Big Data Blog. Use cases 248 AWS IAM Identity Center User Guide Trusted identity propagation with Amazon EMR The following diagram shows a trusted identity propagation conﬁguration for Amazon EMR Studio using Amazon EMR on Amazon EC2 with access control provided by AWS Lake Formation and Amazon S3 Access Grants. Supported client-facing applications • Amazon EMR Studio To enable trusted identity propagation, follow these steps: • Set up Amazon EMR Studio as the client-facing application for Amazon EMR cluster. • Set up Amazon EMR Cluster on Amazon EC2 with Apache Spark. • Recommended: AWS Lake Formation and Amazon S3 Access Grants to provide ﬁne-grained access control to AWS Glue Data Catalog and underlying data locations in S3. Setting up trusted identity propagation with Amazon EMR Studio The following procedure walks you through setting up Amazon EMR Studio for trusted identity propagation in queries against an Amazon Athena workgroups or Amazon EMR clusters running Apache Spark. Prerequisites Before you can get started with this tutorial, you'll need to set up the following: 1. Enable IAM Identity Center. Organization instance is recommended. For more information, see Prerequisites and considerations. 2. Provision the users and groups from your source of identities into IAM Identity Center. Use cases 249 AWS IAM Identity Center User Guide To complete setting up trusted identity propagation from Amazon EMR Studio, the EMR Studio administrator must perform the following steps. Step 1. Create the required IAM roles for EMR Studio In this step, the Amazon EMR Studio administrator creates and IAM service role and an IAM user role for EMR Studio. 1. Create an EMR Studio service role - EMR Studio assume this IAM role to securely manage workspaces and notebooks, connect to clusters, and handle data interactions. a. Navigate to the IAM console (https://console.aws.amazon.com/iam/) and create an IAM role. b. Select AWS service as the trusted entity and then choose Amazon EMR. Attach the following policies to deﬁne the role's permissions and trust relationship. To use these policy, replace the italicized placeholder text in the example policy with your own information. For additional directions, see Create a policy or Edit a policy. { "Version": "2012-10-17", "Statement": [ { "Sid": "ObjectActions", "Effect": "Allow", "Action": [ "s3:PutObject", "s3:GetObject", "s3:DeleteObject" ], "Resource": [ "arn:aws:s3:::Your-S3-Bucket-For-EMR-Studio/*" ], "Condition": { "StringEquals": { "aws:ResourceAccount": "Your-AWS-Account-ID" } } }, { "Sid": "BucketActions", "Effect": "Allow", Use cases 250 AWS IAM Identity Center User Guide "Action": [ "s3:ListBucket", "s3:GetEncryptionConfiguration" ], "Resource": [ "arn:aws:s3:::Your-S3-Bucket-For-EMR-Studio" ], "Condition": { "StringEquals": { "aws:ResourceAccount": "Your-AWS-Account-ID" } } } ] } For a reference of all the service role permissions, see EMR Studio service role permissions. 2. Create an EMR Studio user role for IAM Identity Center authentication - EMR Studio assumes this role when a user signs in through IAM Identity Center to manage workspaces, EMR clusters, jobs, git repositories. This role is used to initiate the trusted identity propagation workﬂow. Note The EMR Studio user role does not need to include permissions to access the Amazon S3 locations of the tables in AWS Glue Catalog. AWS Lake
sso-ug-105	sso-ug.pdf	105	], "Condition": { "StringEquals": { "aws:ResourceAccount": "Your-AWS-Account-ID" } } } ] } For a reference of all the service role permissions, see EMR Studio service role permissions. 2. Create an EMR Studio user role for IAM Identity Center authentication - EMR Studio assumes this role when a user signs in through IAM Identity Center to manage workspaces, EMR clusters, jobs, git repositories. This role is used to initiate the trusted identity propagation workﬂow. Note The EMR Studio user role does not need to include permissions to access the Amazon S3 locations of the tables in AWS Glue Catalog. AWS Lake Formation permissions and registered lake locations will be used to receive temporary permissions. The following example policy can be used in a role allowing a user of EMR Studio to use Athena workgroups to run queries. { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowDefaultEC2SecurityGroupsCreationInVPCWithEMRTags", "Effect": "Allow", "Action": [ "ec2:CreateSecurityGroup" Use cases 251 AWS IAM Identity Center ], "Resource": [ "arn:aws:ec2:::vpc/" ], "Condition": { "StringEquals": { User Guide "aws:ResourceTag/for-use-with-amazon-emr-managed-policies": "true" } } }, { "Sid": "AllowAddingEMRTagsDuringDefaultSecurityGroupCreation", "Effect": "Allow", "Action": [ "ec2:CreateTags" ], "Resource": "arn:aws:ec2:::security-group/", "Condition": { "StringEquals": { "aws:RequestTag/for-use-with-amazon-emr-managed-policies": "true", "ec2:CreateAction": "CreateSecurityGroup" } } }, { "Sid": "AllowSecretManagerListSecrets", "Action": [ "secretsmanager:ListSecrets" ], "Resource": "", "Effect": "Allow" }, { "Sid": "AllowSecretCreationWithEMRTagsAndEMRStudioPrefix", "Effect": "Allow", "Action": "secretsmanager:CreateSecret", "Resource": "arn:aws:secretsmanager:::secret:emr-studio-", "Condition": { "StringEquals": { "aws:RequestTag/for-use-with-amazon-emr-managed-policies": "true" } Use cases 252 AWS IAM Identity Center } }, { User Guide "Sid": "AllowAddingTagsOnSecretsWithEMRStudioPrefix", "Effect": "Allow", "Action": "secretsmanager:TagResource", "Resource": "arn:aws:secretsmanager:::secret:emr-studio-" }, { "Sid": "AllowPassingServiceRoleForWorkspaceCreation", "Action": "iam:PassRole", "Resource": [ "arn:aws:iam::Your-AWS-Account-ID:role/service- role/AmazonEMRStudio_ServiceRole_Name" ], "Effect": "Allow" }, { "Sid": "AllowS3ListAndLocationPermissions", "Action": [ "s3:ListAllMyBuckets", "s3:ListBucket", "s3:GetBucketLocation" ], "Resource": "arn:aws:s3:::", "Effect": "Allow" }, { "Sid": "AllowS3ReadOnlyAccessToLogs", "Action": [ "s3:GetObject" ], "Resource": [ "arn:aws:s3:::aws-logs-Your-AWS-Account-ID-Region/elasticmapreduce/ " ], "Effect": "Allow" }, { "Sid": "AllowAthenaQueryExecutions", "Effect": "Allow", "Action": [ "athena:StartQueryExecution", "athena:GetQueryExecution", Use cases 253 AWS IAM Identity Center User Guide "athena:GetQueryResults", "athena:StopQueryExecution", "athena:ListQueryExecutions", "athena:GetQueryResultsStream", "athena:ListWorkGroups", "athena:GetWorkGroup", "athena:CreatePreparedStatement", "athena:GetPreparedStatement", "athena:DeletePreparedStatement" ], "Resource": "" }, { "Sid": "AllowGlueSchemaManipulations", "Effect": "Allow", "Action": [ "glue:GetDatabase", "glue:GetDatabases", "glue:GetTable", "glue:GetTables", "glue:GetPartition", "glue:GetPartitions" ], "Resource": "" }, { "Sid": "AllowQueryEditorToAccessWorkGroup", "Effect": "Allow", "Action": "athena:GetWorkGroup", "Resource": "arn:aws:athena::Your-AWS-Account-ID:workgroup" }, { "Sid": "AllowConfigurationForWorkspaceCollaboration", "Action": [ "elasticmapreduce:UpdateEditor", "elasticmapreduce:PutWorkspaceAccess", "elasticmapreduce:DeleteWorkspaceAccess", "elasticmapreduce:ListWorkspaceAccessIdentities" ], "Resource": "", "Effect": "Allow", "Condition": { "StringEquals": { "elasticmapreduce:ResourceTag/creatorUserId": "${aws:userId}" Use cases 254 AWS IAM Identity Center User Guide } } }, { "Sid": "DescribeNetwork", "Effect": "Allow", "Action": [ "ec2:DescribeVpcs", "ec2:DescribeSubnets", "ec2:DescribeSecurityGroups" ], "Resource": "" }, { "Sid": "ListIAMRoles", "Effect": "Allow", "Action": [ "iam:ListRoles" ], "Resource": "" }, { "Sid": "AssumeRole", "Effect": "Allow", "Action": [ "sts:AssumeRole" ], "Resource": "*" } ] } The following trust policy allows EMR Studio to assume the role: { "Version": "2008-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "elasticmapreduce.amazonaws.com" }, "Action": [ Use cases 255 AWS IAM Identity Center User Guide "sts:AssumeRole", "sts:SetContext" ] } ] } Note Additional permissions are needed to leverage EMR Studio Workspaces and EMR Notebooks. See Create permissions policies for EMR Studio users for more information. You can ﬁnd more information with the following links: • Deﬁne custom IAM permissions with customer managed policies • EMR Studio service role permissions Step 2. Create and conﬁgure your EMR Studio In this step, you'll create an Amazon EMR Studio in the EMR Studio console and use the IAM roles you created in Step 1. Create the required IAM roles for EMR Studio. 1. Navigate to the EMR Studio console, select Create Studio and the Custom Setup option. You can either create a new S3 bucket or use an existing bucket. You may check the box to Encrypt workspace ﬁles with your own KMS keys. For more information, see AWS Key Management Service. Use cases 256 AWS IAM Identity Center User Guide 2. Under Service role to let Studio access your resources, select the service role created in Step 1. Create the required IAM roles for EMR Studio from the menu. 3. Choose IAM Identity Center under Authentication. Select the user role created in Step 1. Create the required IAM roles for EMR Studio. 4. Check the Trusted identity propagation box. Choose Only assigned users and groups under the Application access section, which will allow you to grant only authorized user and groups to access this studio. 5. (Optional) - You can conﬁgure VPC and subnet if you're using this Studio with EMR clusters. Use cases 257 AWS IAM Identity Center User Guide 6. Review all the details and select Create Studio. 7. After conﬁguring an Athena WorkGroup or EMR clusters, sign in to the Studio's URL to: a. Run Athena queries with the Query Editor. b. Run Spark jobs in the workspace using Jupyter notebook. Trusted identity propagation with Amazon Athena The steps to enable trusted identity propagation depend on whether your users interact with AWS managed applications or customer managed applications. The following diagram shows a trusted identity propagation conﬁguration for client-facing applications - either AWS managed
sso-ug-106	sso-ug.pdf	106	this Studio with EMR clusters. Use cases 257 AWS IAM Identity Center User Guide 6. Review all the details and select Create Studio. 7. After conﬁguring an Athena WorkGroup or EMR clusters, sign in to the Studio's URL to: a. Run Athena queries with the Query Editor. b. Run Spark jobs in the workspace using Jupyter notebook. Trusted identity propagation with Amazon Athena The steps to enable trusted identity propagation depend on whether your users interact with AWS managed applications or customer managed applications. The following diagram shows a trusted identity propagation conﬁguration for client-facing applications - either AWS managed or external to AWS - that uses Amazon Athena to query Amazon S3 data with access control provided by AWS Lake Formation and Amazon S3 Access Grants. Note • Trusted identity propagation with Amazon Athena requires the use of Trino. • Apache Spark and SQL clients connected to Amazon Athena via ODBC and JDBC drivers are not supported. Use cases 258 AWS IAM Identity Center User Guide AWS managed applications The following AWS managed client-facing application supports trusted identity propagation with Athena: • Amazon EMR Studio To enable trusted identity propagation, follow these steps: • Set up Amazon EMR Studio as the client-facing application for Athena. The Query Editor in EMR Studio is needed to run Athena Queries when trusted identity propagation is enabled. • Set up Athena Workgroup. • Set up AWS Lake Formation to enable ﬁne-grained access control for AWS Glue tables based on the user or group in IAM Identity Center. • Set up Amazon S3 Access Grants to enable temporary access to the underlying data locations in S3. Note Both Lake Formation and Amazon S3 Access Grants are required for access control to AWS Glue Data Catalog and for Athena query results in Amazon S3. Customer managed applications Use cases 259 AWS IAM Identity Center User Guide To enable trusted identity propagation for users of custom-developed applications, see to Access AWS services programmatically using trusted identity propagation in the AWS Security Blog. Setting up trusted identity propagation with Amazon Athena workgroups The following procedure walks you through setting up Amazon Athena workgroups for trusted identity propagation. Prerequisites Before you can get started with this tutorial, you'll need to set up the following: 1. Enable IAM Identity Center. Organization instance is recommended. For more information, see Prerequisites and considerations. 2. Provision the users and groups from your source of identities into IAM Identity Center. 3. This conﬁguration requires Amazon EMR Studio, AWS Lake Formation, and Amazon S3 Access Grants. Setting up trusted identity propagation with Athena To set up trusted identity propagation with Athena, the Athena administrator must: 1. Review Considerations and limitations in using IAM Identity Center enabled Athena workgroups. 2. Create an IAM Identity Center enabled Athena workgroup. Authorization services In all analytics and data lakehouse use cases, you can achieve ﬁne-grained access controls using: • AWS Lake Formation - for guidance, see Setting up AWS Lake Formation with IAM Identity Center. • Amazon S3 Access Grants - for guidance, see Setting up Amazon S3 Access Grants with IAM Identity Center. Setting up AWS Lake Formation with IAM Identity Center AWS Lake Formation is a managed service that simpliﬁes the creation and management of data lakes on AWS. It automates data collection, cataloging, and security, providing a centralized Use cases 260 AWS IAM Identity Center User Guide repository for storing and analyzing diverse data types. Lake Formation oﬀers ﬁne-grained access controls and integrates with various AWS analytics services, enabling organizations to eﬃciently set up, secure, and derive insights from their data lakes. Follow these steps to enable Lake Formation to grant data permissions based on user identity using IAM Identity Center and trusted identity propagation. Prerequisites Before you can get started with this tutorial, you'll need to set up the following: • Enable IAM Identity Center. Organization instance is recommended. For more information, see Prerequisites and considerations. Steps to set up trusted identity propagation 1. Integrate IAM Identity Center with AWS Lake Formation following the guidance in Connecting Lake Formation with IAM Identity Center. Important If you do not have AWS Glue Data Catalog tables, you must create them in order to use AWS Lake Formation to grant access to IAM Identity Center users and groups. See Creating objects in AWS Glue Data Catalog for more information. 2. Register data lake locations. Register the S3 locations where the data of the Glue tables are stored. By doing this, Lake Formation will provision temporary access to the required S3 locations when the tables are queried, removing the need to include S3 permissions in the service role (e.g. the Athena service role conﬁgured on the WorkGroup). a. Navigate to the Data lake locations under the Administration section in the navigation pane in the AWS Lake Formation console.
sso-ug-107	sso-ug.pdf	107	Formation to grant access to IAM Identity Center users and groups. See Creating objects in AWS Glue Data Catalog for more information. 2. Register data lake locations. Register the S3 locations where the data of the Glue tables are stored. By doing this, Lake Formation will provision temporary access to the required S3 locations when the tables are queried, removing the need to include S3 permissions in the service role (e.g. the Athena service role conﬁgured on the WorkGroup). a. Navigate to the Data lake locations under the Administration section in the navigation pane in the AWS Lake Formation console. Select Register location. This will allow Lake Formation to provision temporary IAM credentials with the necessary permissions to access S3 data locations. Use cases 261 AWS IAM Identity Center User Guide b. c. Enter the S3 path of the data locations of the AWS Glue tables in the Amazon S3 path ﬁeld. In the IAM role section, do not select the service linked role if you want to use it with trusted identity propagation. Create a separate role with the following permissions. To use these policies, replace the italicized placeholder text in the example policy with your own information. For additional directions, see Create a policy or Edit a policy. The permission policy should grant access to the S3 location speciﬁed in the path: i. Permission policy: { "Version": "2012-10-17", "Statement": [ { "Sid": "LakeFormationDataAccessPermissionsForS3", "Effect": "Allow", "Action": [ "s3:PutObject", "s3:GetObject", "s3:DeleteObject" ], "Resource": [ "arn:aws:s3:::Your-S3-Bucket/" ] }, { Use cases 262 AWS IAM Identity Center User Guide "Sid": "LakeFormationDataAccessPermissionsForS3ListBucket", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::Your-S3-Bucket" ] }, { "Sid": "LakeFormationDataAccessServiceRolePolicy", "Effect": "Allow", "Action": [ "s3:ListAllMyBuckets" ], "Resource": [ "arn:aws:s3:::" ] } ] } ii. Trust relationship: This should include sts:SectContext, which is required for trusted identity propagation. { "Version": "2012-10-17", "Statement": [ { "Sid": "", "Effect": "Allow", "Principal": { "Service": "lakeformation.amazonaws.com" }, "Action": [ "sts:AssumeRole", "sts:SetContext" ] } ] } Use cases 263 AWS IAM Identity Center User Guide Note The IAM role created by the wizard is a service-linked role and does not include sts:SetContext. d. After creating the IAM role, select Register location. Trusted identity propagation with Lake Formation across AWS accounts AWS Lake Formation supports using AWS Resource Access Manager (RAM) to share tables across AWS accounts and it works with trusted identity propagation when the grantor account and grantee account are in the same AWS Region, in the same AWS Organizations, and share the same organization instance of IAM Identity Center. See Cross-account data sharing in Lake Formation for more information. Setting up Amazon S3 Access Grants with IAM Identity Center Amazon S3 Access Grants provides the ﬂexibility to grant identity-based ﬁne-grain access control to S3 locations. You can use Amazon S3 Access Grants to grant Amazon S3 bucket access directly to your corporate users and groups. Follow these steps to enable S3 Access Grants with IAM Identity Center and achieve trusted identity propagation. Prerequisites Before you can get started with this tutorial, you'll need to set up the following: • Enable IAM Identity Center. Organization instance is recommended. For more information, see Prerequisites and considerations. Conﬁguring S3 Access Grants for trusted identity propagation through IAM Identity Center If you already have an Amazon S3 Access Grants instance with a registered location, follow these steps: 1. Associate your IAM Identity Center instance. 2. Create a grant. Use cases 264 AWS IAM Identity Center User Guide If you have not created an Amazon S3 Access Grants yet, follow these steps: 1. Create an S3 Access Grants instance - You can create one S3 Access Grants instance per AWS Region. When you create the S3 Access Grants instance, make sure to check the Add IAM Identity Center instance box and provide the ARN of your IAM Identity Center instance. Select Next. The following image shows the Create S3 Access Grants instance page in the Amazon S3 Access Grants console: 2. Register a location - After you create an create an Amazon S3 Access Grants instance in an AWS Region in your account, you register an S3 location in that instance. An S3 Access Grants location maps the default S3 region (S3://), a bucket, or a preﬁx to an IAM role. S3 Access Grants assumes this Amazon S3 role to vend temporary credentials to the grantee that is accessing that particular location. You must ﬁrst register at least one location in your S3 Access Grants instance before you can create an access grant. For the Location scope, specify s3://, which includes all of your buckets in that Region. This is the recommended location scope for most use cases. If you have an advanced access management use case, you can set the location scope to a speciﬁc bucket s3://bucketor preﬁx within a bucket s3://bucket/prefix-with-path. For more
sso-ug-108	sso-ug.pdf	108	a preﬁx to an IAM role. S3 Access Grants assumes this Amazon S3 role to vend temporary credentials to the grantee that is accessing that particular location. You must ﬁrst register at least one location in your S3 Access Grants instance before you can create an access grant. For the Location scope, specify s3://, which includes all of your buckets in that Region. This is the recommended location scope for most use cases. If you have an advanced access management use case, you can set the location scope to a speciﬁc bucket s3://bucketor preﬁx within a bucket s3://bucket/prefix-with-path. For more information, see Register a location in the Amazon Simple Storage Service User Guide. Use cases 265 AWS IAM Identity Center Note User Guide Ensure the S3 locations of the AWS Glue tables you want to grant access to are included in this path. The procedure requires you to conﬁgure an IAM role for the location. This role should include permissions to access the location scope. You can use the S3 console wizard to create the role. You'll need to specify your S3 Access Grants instance ARN in the policies for this IAM role. The default value of your S3 Access Grants instance ARN is arn:aws:s3:Your-Region:Your- AWS-Account-ID:access-grants/default. The following example permission policy gives Amazon S3 permissions to the IAM role that you created. And the example trust policy following it allows the S3 Access Grants service principal to assume the IAM role. a. Permission policy To use these policies, replace the italicized placeholder text in the example policy with your own information. For additional directions, see Create a policy or Edit a policy. { "Version":"2012-10-17", "Statement": [ { "Sid": "ObjectLevelReadPermissions", "Effect":"Allow", "Action":[ "s3:GetObject", "s3:GetObjectVersion", "s3:GetObjectAcl", "s3:GetObjectVersionAcl", "s3:ListMultipartUploadParts" ], "Resource":[ "arn:aws:s3:::" ], "Condition":{ Use cases 266 AWS IAM Identity Center User Guide "StringEquals": { "aws:ResourceAccount": "Your-AWS-Account-ID" }, "ArnEquals": { "s3:AccessGrantsInstanceArn": ["Your-Custom-Access-Grants- Location-ARN"] } } }, { "Sid": "ObjectLevelWritePermissions", "Effect":"Allow", "Action":[ "s3:PutObject", "s3:PutObjectAcl", "s3:PutObjectVersionAcl", "s3:DeleteObject", "s3:DeleteObjectVersion", "s3:AbortMultipartUpload" ], "Resource":[ "arn:aws:s3:::" ], "Condition":{ "StringEquals": { "aws:ResourceAccount": "Your-AWS-Account-ID" }, "ArnEquals": { "s3:AccessGrantsInstanceArn": ["Your-Custom-Access-Grants- Location-ARN"] } } }, { "Sid": "BucketLevelReadPermissions", "Effect":"Allow", "Action":[ "s3:ListBucket" ], "Resource":[ "arn:aws:s3:::" ], "Condition":{ "StringEquals": { "aws:ResourceAccount": "Your-AWS-Account-ID" }, "ArnEquals": { "s3:AccessGrantsInstanceArn": ["Your-Custom-Access-Grants- Location-ARN"] } Use cases 267 AWS IAM Identity Center } User Guide }, //Optionally add the following section if you use SSE-KMS encryption { "Sid": "KMSPermissions", "Effect":"Allow", "Action":[ "kms:Decrypt", "kms:GenerateDataKey" ], "Resource":[ "" ] } ] } b. Trust policy In the IAM role trust policy, give the S3 Access Grants service (access- grants.s3.amazonaws.com) principal access to the IAM role that you created. To do so, you can create a JSON ﬁle that contains the following statements. To add the trust policy to your account, see Create a role using custom trust policies. { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1234567891011", "Effect": "Allow", "Principal": { "Service":"access-grants.s3.amazonaws.com" }, "Action": [ "sts:AssumeRole", "sts:SetSourceIdentity" ], "Condition": { "StringEquals": { "aws:SourceAccount":"Your-AWS-Account-ID", "aws:SourceArn":"Your-Custom-Access-Grants-Location-ARN" } } Use cases 268 AWS IAM Identity Center }, User Guide //For an IAM Identity Center use case, add: { "Sid": "Stmt1234567891012", "Effect": "Allow", "Principal": { "Service": "access-grants.s3.amazonaws.com" }, "Action": "sts:SetContext", "Condition":{ "StringEquals":{ "aws:SourceAccount":"Your-AWS-Account-ID", "aws:SourceArn":"Your-Custom-Access-Grants-Location-ARN" }, "ForAllValues:ArnEquals": { "sts:RequestContextProviders":"arn:aws:iam::aws:contextProvider/ IdentityCenter" } } } ] } Create an Amazon S3 Access Grant If you have an Amazon S3 Access Grants instance with a registered location and you have associated your IAM Identity Center instance with it, you can create a grant. In the S3 console Create Grant page, complete the following: Create a grant 1. Select the location created in the previous step. You can reduce the scope of the grant by adding a sub-preﬁx. The sub-preﬁx can be a bucket, bucket/prefix, or an object in the bucket. For more information, see Subpreﬁx in the Amazon Simple Storage Service User Guide. 2. Under Permissions and access, select Read and or Write depending on your needs. 3. In Granter type, choose Directory Identity form IAM Identity Center. 4. Provide the IAM Identity Center User or Group ID. You can ﬁnd the user and group IDs in the IAM Identity Center console under User and Group sections. Select Next. 5. On the Review and Finish page, review the settings for the S3 Access Grant and then select Create Grant. Use cases 269 AWS IAM Identity Center User Guide The following image shows the Create Grant page in the Amazon S3 Access Grants console: Using trusted identity propagation with customer managed applications Trusted identity propagation enables a customer managed application to request access to data in AWS services on behalf of a user. Data access management is based on a user’s identity, so administrators can grant access based on users' existing user and group memberships. The user's identity, actions performed on their behalf, and other events are recorded in service-speciﬁc logs and CloudTrail events. With trusted identity propagation, a user can sign in
sso-ug-109	sso-ug.pdf	109	AWS IAM Identity Center User Guide The following image shows the Create Grant page in the Amazon S3 Access Grants console: Using trusted identity propagation with customer managed applications Trusted identity propagation enables a customer managed application to request access to data in AWS services on behalf of a user. Data access management is based on a user’s identity, so administrators can grant access based on users' existing user and group memberships. The user's identity, actions performed on their behalf, and other events are recorded in service-speciﬁc logs and CloudTrail events. With trusted identity propagation, a user can sign in to a customer managed application, and that application can pass the user's identity in requests to access data in AWS services. Important To access an AWS service, customer managed applications must obtain a token from a trusted token issuer, which is external to IAM Identity Center. A trusted token issuer is an OAuth 2.0 authorization server that creates signed tokens. These tokens authorize applications that initiate requests for access to AWS services (receiving applications). For more information, see Using applications with a trusted token issuer. Customer managed applications 270 AWS IAM Identity Center Topics User Guide • Set up customer managed OAuth 2.0 applications for trusted identity propagation • Specify trusted applications • Using applications with a trusted token issuer Set up customer managed OAuth 2.0 applications for trusted identity propagation To set up a customer managed OAuth 2.0 application for trusted identity propagation, you must ﬁrst add it to IAM Identity Center. Use the following procedure to add your application to IAM Identity Center. Topics • Step 1: Select application type • Step 2: Specify application details • Step 3: Specify authentication settings • Step 4: Specify application credentials • Step 5: Review and conﬁgure Step 1: Select application type 1. Open the IAM Identity Center console. 2. Choose Applications. 3. Choose the Customer managed tab. 4. Choose Add application. 5. On the Select application type page, under Setup preference, choose I have an application I want to set up. 6. Under Application type, choose OAuth 2.0. 7. Choose Next to proceed to the next page, Step 2: Specify application details. Step 2: Specify application details 1. On the Specify application details page, under Application name and description, enter a Display name for the application, such as MyApp. Then, enter a Description. Customer managed applications 271 AWS IAM Identity Center User Guide 2. Under User and group assignment method, choose one of the following options: • Require assignments – Allow only IAM Identity Center users and groups who are assigned to this application to access the application. Application tile visibility –Only users who are assigned to the application directly or through a group assignment can view the application tile in the AWS access portal, provided that Application visibility in AWS access portal is set to Visible. • Do not require assignments – Allow all authorized IAM Identity Center users and groups to access this application. Application tile visibility – The application tile is visible to all users who sign in to the AWS access portal, unless Application visibility in AWS access portal is set to Not visible. 3. Under AWS access portal, enter the URL where users can access the application and specify whether the application tile will be visible or not visible in the AWS access portal. If you choose Not visible, not even assigned users can view the application tile. 4. Under Tags (optional), choose Add new tag, and then specify values for Key and Value (optional). For information about tags, see Tagging AWS IAM Identity Center resources. 5. Choose Next, and proceed to the next page, Step 3: Specify authentication settings. Step 3: Specify authentication settings To add a customer managed application that supports OAuth 2.0 to IAM Identity Center, you must specify a trusted token issuer. A trusted token issuer is an OAuth 2.0 authorization server that creates signed tokens. These tokens authorize applications that initiate requests (requesting applications) for access to AWS managed applications (receiving applications). 1. On the Specify authentication settings page, under Trusted token issuers, do either of the following: • To use an existing trusted token issuer: Select the check box next to the name of the trusted token issuer that you want to use. • To add a new trusted token issuer: 1. Choose Create trusted token issuer. Customer managed applications 272 AWS IAM Identity Center User Guide 2. A new browser tab opens. Follow steps 5 through 8 in How to add a trusted token issuer to the IAM Identity Center console. 3. After you complete these steps, return to the browser window that you are using for your application setup and select the trusted token issuer that you just added. 4. In the list of trusted token issuers,
sso-ug-110	sso-ug.pdf	110	next to the name of the trusted token issuer that you want to use. • To add a new trusted token issuer: 1. Choose Create trusted token issuer. Customer managed applications 272 AWS IAM Identity Center User Guide 2. A new browser tab opens. Follow steps 5 through 8 in How to add a trusted token issuer to the IAM Identity Center console. 3. After you complete these steps, return to the browser window that you are using for your application setup and select the trusted token issuer that you just added. 4. In the list of trusted token issuers, select the check box next to the name of the trusted token issuer that you just added. After you select a trusted token issuer, the Conﬁgure selected trusted token issuers section appears. 2. Under Conﬁgure selected trusted token issuers, enter the Aud claim. The Aud claim identiﬁes the intended audience (recipients) for the token that is generated by the trusted token issuer. For more information, see Aud claim. 3. To prevent your users from having to reauthenticate when they are using this application, select Enable refresh token grant. When selected, this option refreshes the access token for the session every 60 minutes, until the session expires or the user ends the session. 4. Choose Next, and proceed to the next page, Step 4: Specify application credentials. Step 4: Specify application credentials Complete the steps in this procedure to specify the credentials that your application uses to perform token exchange actions with trusted applications. These credentials are used in a resource- based policy. The policy requires that you specify a principal that has permissions to perform the actions that are speciﬁed in the policy. You must specify a principal, even if the trusted applications are in the same AWS account. Note When you set permissions with policies, grant only the permissions required to perform a task. You do this by deﬁning the actions that can be taken on speciﬁc resources under speciﬁc conditions, also known as least-privilege permissions. This policy requires the sso-oauth:CreateTokenWithIAM action. 1. On the Specify application credentials page, do either of the following: • To quickly specify one or more IAM roles: Customer managed applications 273 AWS IAM Identity Center User Guide 1. Choose Enter one or more IAM roles. 2. Under Enter IAM roles, specify the Amazon Resource Name (ARN) of an existing IAM role. To specify the ARN, use the following syntax. The Region portion of the ARN is blank because IAM resources are global. arn:aws:iam::account:role/role-name-with-path For more information, see Cross-account access using resource-based policies and IAM ARNs in the AWS Identity and Access Management User Guide. • To manually edit the policy (required if you specify non-AWS credentials): 1. Select Edit the application policy. 2. Modify your policy by typing or pasting text in the JSON text box. 3. Resolve any security warnings, errors, or general warnings generated during policy validation. For more information see Validating IAM policies in the AWS Identity and Access Management User Guide. 2. Choose Next and proceed to the next page, Step 5: Review and conﬁgure. Step 5: Review and conﬁgure 1. On the Review and conﬁgure page, review the choices that you made. To make changes, choose the conﬁguration section that you want, choose Edit, and then make the required changes. 2. After you're ﬁnished, choose Add application. 3. The application that you added appears in the Customer managed applications list. 4. After you set up your customer managed application in IAM Identity Center, you must specify one or more AWS services, or trusted applications, for identity propagation. This enables users to sign in to your customer managed application and access data in the trusted application. For more information, see Specify trusted applications . Specify trusted applications After you set up your customer managed application, you must specify one or more trusted AWS services, or trusted applications, for identity propagation. Specify an AWS service that has data that users of your customer managed applications need to access. When your users sign in to Customer managed applications 274 AWS IAM Identity Center User Guide your customer managed application, that application will pass your users' identity to the trusted application. Use the following procedure to select a service, and then specify individual applications to trust for that service. 1. Open the IAM Identity Center console. 2. Choose Applications. 3. Choose the Customer managed tab. 4. In the Customer managed applications list, select the OAuth 2.0 application that you want to initiate requests for access. This is the application that your users sign in to. 5. On the Details page, under Trusted applications for identity propagation, choose Specify trusted applications. 6. Under Setup type, select Individual applications and specify access, and then choose Next. 7. On the Select service page, choose the
sso-ug-111	sso-ug.pdf	111	the following procedure to select a service, and then specify individual applications to trust for that service. 1. Open the IAM Identity Center console. 2. Choose Applications. 3. Choose the Customer managed tab. 4. In the Customer managed applications list, select the OAuth 2.0 application that you want to initiate requests for access. This is the application that your users sign in to. 5. On the Details page, under Trusted applications for identity propagation, choose Specify trusted applications. 6. Under Setup type, select Individual applications and specify access, and then choose Next. 7. On the Select service page, choose the AWS service that has applications that your customer managed application can trust for identity propagation, and then choose Next. The service that you select deﬁnes the applications that can be trusted. You'll select applications in the next step. 8. On the Select applications page, choose Individual applications, select the check box for each application that can receive requests for access, and then choose Next. 9. On the Conﬁgure access page, under Conﬁguration method, do either of the following: • Select access per application – Select this option to conﬁgure diﬀerent access levels for each application. Choose the application for which you want to conﬁgure the access level, and then choose Edit access. In Level of access to apply, change the access levels as needed, and then choose Save changes. • Apply same level of access to all applications – Select this option if you don't need to conﬁgure access levels on a per-application basis. 10. Choose Next. 11. On the Review conﬁguration page, review the choices that you made. To make changes, choose the conﬁguration section that you want, choose Edit access, and then make the required changes. 12. After you're ﬁnished, choose Trust applications. Customer managed applications 275 AWS IAM Identity Center User Guide Using applications with a trusted token issuer Trusted token issuers enable you to use trusted identity propagation with applications that authenticate outside of AWS. With trusted token issuers, you can authorize these applications to make requests on behalf of their users to access AWS managed applications. The following topics describe how trusted token issuers work and provide setup guidance. Topics • Trusted token issuer overview • Prerequisites and considerations for trusted token issuers • JTI claim details • Trusted token issuer conﬁguration settings • Setting up a trusted token issuer • Identity-enhanced IAM role sessions Trusted token issuer overview Trusted identity propagation provides a mechanism that enables applications that authenticate outside of AWS to make requests on behalf of their users with the use of a trusted token issuer. A trusted token issuer is an OAuth 2.0 authorization server that creates signed tokens. These tokens authorize applications that initiate requests (requesting applications) for access to AWS services(receiving applications). Requesting applications initiate access requests on behalf of users that the trusted token issuer authenticates. The users are known to both the trusted token issuer and IAM Identity Center. AWS services that receive requests manage ﬁne-grained authorization to their resources based on their users and group membership as represented in the Identity Center directory. AWS services can't use the tokens from the external token issuer directly. To solve this, IAM Identity Center provides a way for the requesting application, or an AWS driver that the requesting application uses, to exchange the token issued by the trusted token issuer for a token that is generated by IAM Identity Center. The token that is generated by IAM Identity Center refers to the corresponding IAM Identity Center user. The requesting application, or the driver, uses the new token to initiate a request to the receiving application. Because the new token references the corresponding user in IAM Identity Center, the receiving application can authorize Customer managed applications 276 AWS IAM Identity Center User Guide the requested access based on the user or their group membership as represented in IAM Identity Center. Important Choosing an OAuth 2.0 authorization server to add as a trusted token issuer is a security decision that requires careful consideration. Only choose trusted token issuers that you trust to perform the following tasks: • Authenticate the user who is speciﬁed in the token. • Authorize that user’s access to the receiving application. • Generate a token that IAM Identity Center can exchange for an IAM Identity Center created token. Prerequisites and considerations for trusted token issuers Before you set up a trusted token issuer, review the following prerequisites and considerations. • Trusted token issuer conﬁguration You must conﬁgure an OAuth 2.0 authorization server (the trusted token issuer). Although the trusted token issuer is typically the identity provider that you use as your identity source for IAM Identity Center, it doesn’t have to be. For information about how to set up the trusted token issuer, see the documentation for
sso-ug-112	sso-ug.pdf	112	to the receiving application. • Generate a token that IAM Identity Center can exchange for an IAM Identity Center created token. Prerequisites and considerations for trusted token issuers Before you set up a trusted token issuer, review the following prerequisites and considerations. • Trusted token issuer conﬁguration You must conﬁgure an OAuth 2.0 authorization server (the trusted token issuer). Although the trusted token issuer is typically the identity provider that you use as your identity source for IAM Identity Center, it doesn’t have to be. For information about how to set up the trusted token issuer, see the documentation for the relevant identity provider. Note You can conﬁgure up to 10 trusted token issuers for use with IAM Identity Center, as long you map the identity of each user in the trusted token issuer to a corresponding user in IAM Identity Center. • The OAuth 2.0 authorization server (the trusted token issuer) that creates the token must have an OpenID Connect (OIDC) discovery endpoint that IAM Identity Center can use to obtain public keys to verify the token signatures. For more information, see OIDC discovery endpoint URL (issuer URL). • Tokens issued by the trusted token issuer Tokens from the trusted token issuer must meet the following requirements: Customer managed applications 277 AWS IAM Identity Center User Guide • The token must be signed and in JSON Web Token (JWT) format using the RS256 algorithm. • The token must contain the following claims: • Issuer (iss) – The entity that issued the token. This value must match the value that is conﬁgured in the OIDC discovery endpoint (issuer URL) in the trusted token issuer. • Subject (sub) – The authenticated user. • Audience (aud) – The intended recipient of the token. This is the AWS service that will be accessed after the token is exchanged for a token from IAM Identity Center. For more information, see Aud claim. • Expiration Time (exp) – The time after which the token expires. • The token can be an identity token or an access token. • The token must have an attribute that can be mapped uniquely to one IAM Identity Center user. Note Using a custom signing key for JWTs from Microsoft Entra ID is not supported. In order to use tokens from Microsoft Entra ID with trusted token issuer, you can't use a custom signing key. • Optional claims IAM Identity Center supports all optional claims that are deﬁned in RFC 7523. For more information, see Section 3: JWT Format and Processing Requirements of this RFC. For example, the token can contain a JTI (JWT ID) claim. This claim, when present, prevents tokens that have the same JTI from being reused for token exchanges. For more information about JTI claims, see JTI claim details. • IAM Identity Center conﬁguration to work with a trusted token issuer You must also enable IAM Identity Center, conﬁgure the identity source for IAM Identity Center, and provision users that correspond to the users in the trusted token issuer’s directory. To do this, you must do either of the following: • Synchronize users into IAM Identity Center by using the System for Cross-domain Identity Management (SCIM) 2.0 protocol. • Create the users directly in IAM Identity Center. Customer managed applications 278 AWS IAM Identity Center JTI claim details User Guide If IAM Identity Center receives a request to exchange a token that IAM Identity Center has already exchanged, the request fails. To detect and prevent reuse of a token for token exchanges, you can include a JTI claim. IAM Identity Center protects against the replay of tokens based on the claims in the token. Not all OAuth 2.0 authorization servers add a JTI claim to tokens. Some OAuth 2.0 authorization servers might not allow you to add a JTI as a custom claim. OAuth 2.0 authorization servers that support the use of a JTI claim might add this claim to identity tokens only, access tokens only, or both. For more information, see the documentation for your OAuth 2.0 authorization server. For information about building applications that exchange tokens, see the IAM Identity Center API documentation. For information about conﬁguring a customer managed application to obtain and exchange the correct tokens, see the documentation for the application. Trusted token issuer conﬁguration settings The following sections describe the settings required to set up and use a trusted token issuer. Topics • OIDC discovery endpoint URL (issuer URL) • Attribute mapping • Aud claim OIDC discovery endpoint URL (issuer URL) When you add a trusted token issuer to the IAM Identity Center console, you must specify the OIDC discovery endpoint URL. This URL is commonly referred to by its relative URL, /.well-known/ openid-configuration. In the IAM Identity Center console, this URL is called the issuer URL. Note You must
sso-ug-113	sso-ug.pdf	113	exchange the correct tokens, see the documentation for the application. Trusted token issuer conﬁguration settings The following sections describe the settings required to set up and use a trusted token issuer. Topics • OIDC discovery endpoint URL (issuer URL) • Attribute mapping • Aud claim OIDC discovery endpoint URL (issuer URL) When you add a trusted token issuer to the IAM Identity Center console, you must specify the OIDC discovery endpoint URL. This URL is commonly referred to by its relative URL, /.well-known/ openid-configuration. In the IAM Identity Center console, this URL is called the issuer URL. Note You must paste the URL of the discovery endpoint up until and without .well-known/ openid-configuration. If .well-known/openid-configuration is included in the URL, the trusted token issuer conﬁguration won't work. Because IAM Identity Center doesn't validate this URL, if the URL isn't correctly formed, the trusted token issuer setup will fail without notiﬁcation. Customer managed applications 279 AWS IAM Identity Center User Guide The OIDC discovery endpoint URL must be reachable via ports 80 and 443 only. IAM Identity Center uses this URL to obtain additional information about the trusted token issuer. For example, IAM Identity Center uses this URL to obtain the information required to verify the tokens that the trusted token issuer generates. When you add a trusted token issuer to IAM Identity Center, you must specify this URL. To ﬁnd the URL, see the documentation for the OAuth 2.0 authorization server provider that you use to generate tokens for your application, or contact the provider directly for assistance. Attribute mapping Attribute mappings enable IAM Identity Center to match the user that is represented in a token issued by a trusted token issuer to a single user in IAM Identity Center. You must specify the attribute mapping when you add the trusted token issuer to IAM Identity Center. This attribute mapping is used in a claim in the token that is generated by the trusted token issuer. The value in the claim is used to search IAM Identity Center. The search uses the speciﬁed attribute to retrieve a single user in IAM Identity Center, who will be used as the user within AWS. The claim that you choose must be mapped to one attribute in a ﬁxed list of available attributes in the IAM Identity Center identity store. You can choose one of the following IAM Identity Center identity store attributes: user name, email, and external ID. The value for the attribute that you specify in IAM Identity Center must be unique for each user. Aud claim An aud claim identiﬁes the audience (recipients) for which a token is intended. When the application requesting access authenticates through an identity provider that is not federated to IAM Identity Center, that identity provider must be set up as a trusted token issuer. The application that receives the access request (the receiving application) must exchange the token that is generated by the trusted token issuer for a token that is generated by IAM Identity Center. For information about how to obtain the aud claim values for the receiving application as they are registered in the trusted token issuer, see the documentation for your trusted token issuer or contact the trusted token issuer administrator for assistance. Setting up a trusted token issuer To enable trusted identity propagation for an application that authenticates externally to IAM Identity Center, one or more administrators must set up a trusted token issuer. A trusted token issuer is an OAuth 2.0 authorization server that issues tokens to applications that initiate requests Customer managed applications 280 AWS IAM Identity Center User Guide (requesting applications). The tokens authorize these applications to initiate requests on behalf of their users to a receiving application (an AWS service). Topics • Coordinating administrative roles and responsibilities • Tasks for setting up a trusted token issuer • How to add a trusted token issuer to the IAM Identity Center console • How to view or edit trusted token issuer settings in the IAM Identity Center console • Setup process and request ﬂow for applications that use a trusted token issuer Coordinating administrative roles and responsibilities In some cases, a single administrator might perform all of the necessary tasks for setting up a trusted token issuer. If multiple administrators perform these tasks, close coordination is required. The following table describes how multiple administrators might coordinate to set up a trusted token issuer and conﬁgure AWS service to use it. Note The application can be any AWS service that is integrated with IAM Identity Center and supports trusted identity propagation. For more information, see Tasks for setting up a trusted token issuer. Role Performs these tasks Coordinates with IAM Identity Center administr ator Adds the external IdP as a trusted token issuer to the IAM Identity Center console. External
sso-ug-114	sso-ug.pdf	114	tasks for setting up a trusted token issuer. If multiple administrators perform these tasks, close coordination is required. The following table describes how multiple administrators might coordinate to set up a trusted token issuer and conﬁgure AWS service to use it. Note The application can be any AWS service that is integrated with IAM Identity Center and supports trusted identity propagation. For more information, see Tasks for setting up a trusted token issuer. Role Performs these tasks Coordinates with IAM Identity Center administr ator Adds the external IdP as a trusted token issuer to the IAM Identity Center console. External IdP (trusted token issuer) administrator AWS service administrator Helps set up the correct attribute mapping between IAM Identity Center and the external IdP. Notiﬁes the AWS service administr ator when the trusted token issuer Customer managed applications 281 AWS IAM Identity Center User Guide Role Performs these tasks Coordinates with is added to the IAM Identity Center console. External IdP (trusted token issuer) administr ator Conﬁgures the external IdP to issue tokens. IAM Identity Center administrator AWS service administrator Helps set up the correct attribute mapping between IAM Identity Center and the external IdP. Provides the audience name (Aud claim) to the AWS service administrator. IAM Identity Center administrator External IdP (trusted token issuer) administrator AWS service administrator Checks the AWS service console for the trusted token issuer. The trusted token issuer will be visible in the AWS service console after the IAM Identity Center administr ator adds it to the IAM Identity Center console. Conﬁgures the AWS service to use the trusted token issuer. Tasks for setting up a trusted token issuer To set up a trusted token issuer, an IAM Identity Center administrator, external IdP (trusted token issuer) administrator, and application administrator must complete the following tasks. Note The application can be any AWS service that is integrated with IAM Identity Center and supports trusted identity propagation. Customer managed applications 282 AWS IAM Identity Center User Guide 1. Add the trusted token issuer to IAM Identity Center – The IAM Identity Center administrator adds the trusted token issuer by using the IAM Identity Center console or APIs. This conﬁguration requires specifying the following: • A name for the trusted token issuer. • The OIDC discovery endpoint URL (in the IAM Identity Center console, this URL is called the issuer URL). The discovery endpoint must be reachable via ports 80 and 443 only. • Attribute mapping for user lookup. This attribute mapping is used in a claim in the token that is generated by the trusted token issuer. The value in the claim is used to search IAM Identity Center. The search uses the speciﬁed attribute to retrieve a single user in IAM Identity Center. 2. Connect the AWS service to IAM Identity Center – The AWS service administrator must connect the application to IAM Identity Center by using the console for the application or the application APIs. After the trusted token issuer is added to the IAM Identity Center console, it is also visible in the AWS service console and available for the AWS service administrator to select. 3. Conﬁgure the use of token exchange – In the AWS service console, the AWS service administrator conﬁgures AWS service to accept tokens issued by the trusted token issuer. These tokens are exchanged for tokens generated by IAM Identity Center. This requires specifying the name of the trusted token issuer from Step 1, and the Aud claim value that corresponds to the AWS service. The trusted token issuer places the Aud claim value in the token it issues to indicate that the token is intended for use by the AWS service. To obtain this value, contact the administrator for the trusted token issuer. How to add a trusted token issuer to the IAM Identity Center console In an organization that has multiple administrators, this task is performed by an IAM Identity Center administrator. If you are the IAM Identity Center administrator, you must choose which external IdP to use as a trusted token issuer. To add a trusted token issuer to the IAM Identity Center console 1. Open the IAM Identity Center console. 2. Choose Settings. Customer managed applications 283 AWS IAM Identity Center User Guide 3. On the Settings page, choose the Authentication tab. 4. Under Trusted token issuers, choose Create trusted token issuer. 5. On the Set up an external IdP to issue trusted tokens page, under Trusted token issuer details, do the following: • For Issuer URL, specify the OIDC discovery URL of the external IdP that will issue tokens for trusted identity propagation. You must specify the URL of the discovery endpoint up until and without .well-known/openid-configuration. The administrator of the external IdP can provide this URL. Note Note This URL must match the URL in
sso-ug-115	sso-ug.pdf	115	AWS IAM Identity Center User Guide 3. On the Settings page, choose the Authentication tab. 4. Under Trusted token issuers, choose Create trusted token issuer. 5. On the Set up an external IdP to issue trusted tokens page, under Trusted token issuer details, do the following: • For Issuer URL, specify the OIDC discovery URL of the external IdP that will issue tokens for trusted identity propagation. You must specify the URL of the discovery endpoint up until and without .well-known/openid-configuration. The administrator of the external IdP can provide this URL. Note Note This URL must match the URL in the Issuer (iss) claim in tokens that are issued for trusted identity propagation. • For Trusted token issuer name, enter a name to identify this trusted token issuer in IAM Identity Center and in the application console. 6. Under Map attributes, do the following: • For Identity provider attribute, select an attribute from the list to map to an attribute in the IAM Identity Center identity store. • For IAM Identity Center attribute, select the corresponding attribute for the attribute mapping. 7. Under Tags (optional), choose Add new tag, specify a value for Key, and optionally for Value. For information about tags, see Tagging AWS IAM Identity Center resources. 8. Choose Create trusted token issuer. 9. After you ﬁnish creating the trusted token issuer, contact the application administrator to let them know the name of the trusted token issuer, so that they can conﬁrm that the trusted token issuer is visible in the applicable console. 10. The application administrator must select this trusted token issuer in the applicable console to enable user access to the application from applications that are conﬁgured for trusted identity propagation. Customer managed applications 284 AWS IAM Identity Center User Guide How to view or edit trusted token issuer settings in the IAM Identity Center console After you add a trusted token issuer to the IAM Identity Center console, you can view and edit the relevant settings. If you plan to edit the trusted token issuer settings, keep in mind that doing so might cause users to lose access to any applications that are conﬁgured to use the trusted token issuer. To avoid disrupting user access, we recommend that you coordinate with the administrators for any applications that are conﬁgured to use the trusted token issuer before you edit settings. To view or edit trusted token issuer settings in the IAM Identity Center console 1. Open the IAM Identity Center console. 2. Choose Settings. 3. On the Settings page, choose the Authentication tab. 4. Under Trusted token issuers, select the trusted token issuer that you want to view or edit. 5. Choose Actions, and then choose Edit. 6. On the Edit trusted token issuer page, view or edit settings as needed. You can edit the trusted token issuer name, attribute mappings, and tags. 7. Choose Save changes. 8. In the Edit trusted token issuer dialog box, you're prompted to conﬁrm that you want to make changes. Choose Conﬁrm. Setup process and request ﬂow for applications that use a trusted token issuer This section describes the setup process and request ﬂow for applications that use a trusted token issuer for trusted identity propagation. The following diagram provides an overview of this process. Customer managed applications 285 AWS IAM Identity Center User Guide The following steps provide additional information about this process. 1. Set up IAM Identity Center and the receiving AWS managed application to use a trusted token issuer. For information, see Tasks for setting up a trusted token issuer. 2. The request ﬂow begins when a user opens the requesting application. 3. The requesting application requests a token from the trusted token issuer to initiate requests to the receiving AWS managed application. If the user hasn't authenticated yet, this process triggers an authentication ﬂow. The token contains the following information: • The subject (Sub) of the user. • The attribute that IAM Identity Center uses to look up the corresponding user in IAM Identity Center. • An audience (Aud) claim that contains a value that the trusted token issuer associates with the receiving AWS managed application. If other claims are present, they aren't used by IAM Identity Center. 4. The requesting application, or the AWS driver that it uses, passes the token to IAM Identity Center and requests that the token be exchanged for a token that is generated by IAM Identity Center. If you use an AWS driver, you might need to conﬁgure the driver for this use case. For more information, see the documentation for the relevant AWS managed application. 5. IAM Identity Center uses the OIDC Discovery endpoint to obtain the public key that it can use to verify the authenticity of the token. IAM Identity Center then does the following: Customer managed

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.