Skip to content

Example of Single Sign-On via AWS IAM Identity Center


AWS IAM Identity Center (formerly known as AWS SSO) is a centralized identity management service provided by AWS, supporting Single Sign-On (SSO) to uniformly control user access permissions for multiple AWS accounts, cloud applications (such as Salesforce, GitHub), and hybrid cloud resources.

Note: The SAML 2.0 single sign-on feature of AWS IAM Identity Center is only available for use on the AWS international site.

1. Enable IAM Identity Center

In this example, it is assumed that the user account logging into the AWS platform has never used the IAM Identity Center service before, and this will be its first use.

  1. Log in to the AWS console;
  2. In the search bar, type IAM Identity Center;
  3. Click "Enable".

Note:

  • When enabling IAM Identity Center, pay attention to the region selection in the top navigation bar of the console. Once the service is enabled, it cannot be directly switched regions; you must re-enable and reconfigure all settings in the new region;
  • If your organization already has an AWS main management region (such as us-east-1 or ap-northeast-1), it is recommended to maintain consistency for easier unified management.

2. Create a Custom SAML 2.0 Application

On the application management page, select "Customer-managed," and click "Add application."

Why choose 'Customer-managed (Custom)'
Option Applicable Scenario
AWS-managed Third-party SaaS applications pre-integrated by AWS (such as Salesforce, Slack, Zoom). AWS automatically provides metadata and configuration templates.
Customer-managed Third-party platforms requiring manual SAML configuration (non-AWS pre-integrated applications, such as the example object 'Guance platform' in this article), requiring self-provisioning of SAML metadata or ACS URL.
  1. Select the application type as "I want to set up my own application";
  2. Continue selecting SAML 2.0, proceed to the next step.

Configure the Application

  1. Define the display name for this application, such as Guance;
  2. Enter a description as needed;
  3. Under "IAM Identity Center Metadata," click to download the IAM Identity Center SAML metadata file and certificate;
  4. Under application metadata, select "Upload application SAML metadata file," here choose the metadata file downloaded from Guance;
  5. Submit the current configuration;
  6. The page will prompt that the application was successfully added.

3. Edit Attribute Mapping

Attribute mapping is the core configuration of SAML integration, used to pass AWS user attributes to Guance.

After returning to the application details page, click Actions > Edit attribute mappings in the upper right corner of the page to map the user login identity in AWS with the role identity in Guance.

  1. The system default provides the field Subject (user unique identifier), choose to map it to ${user:email};
  2. After configuring, click save changes.

Additional Role Attributes

  1. Define the user or group attributes to be mapped to roles, here select email, familyName two fields;
  2. Define the attributes mapped to these string values, respectively $(user:email}, $(user:familyName};
  3. Save the current changes.
  4. Subsequently, go to Guance to configure role mapping.

4. Assign User and Group Access Permissions

The users and groups you create in the Identity Center directory are only available in IAM Identity Center. You can assign permissions to them later. In this example, by default, no users or groups have been added to the current directory.

Step 1: Add Users

  1. Go to the console > Users page;
  2. Click "Add users";
  3. Define the username, select how the user receives the password, and input email, first name, last name, display name;
  4. Proceed to the next step.

Note: The username, password, and email configured here are required for subsequent single sign-on for this user.

Step 2: Add Users to Groups

  1. If there are no groups in the current directory, enter the creation entry on the right side;
  2. Define the group name;
  3. Click the "Create" button in the lower right corner;
  4. Return to the add users page, select this group, proceed to the next step;
  5. Confirm adding this user. The status message will notify you that you have successfully added the user.

Step 3: Assign Users and Groups to the Application

  1. Go to the application, select the configured program (in this example, the previously configured Guance), and assign users and groups to it;
  2. Search and check all users and groups that need permission assignment;
  3. After reviewing, the assignment will be successful.

5. Create a User SSO Identity Provider in Guance

  1. Log in and enter Guance workspace > Manage > Member Management > User SSO;
  2. Select SAML;
  3. Click Add Identity Provider, start configuration;
  4. Define the identity provider name as aws_sso;
  5. Upload the metadata document downloaded when configuring the application;
  6. Define access restrictions as guance.com;
  7. Select roles and session duration;
  8. Click confirm.

For more configuration details here, refer to SSO Management.

6. Login Verification

  1. Log in and enter Guance single sign-on page: https://auth.guance.com/login/sso;
  2. Select the application created on the AWS side in the list;
  3. Login address;
  4. Input username, password;
  5. Successful login.

Feedback

Is this page helpful? ×