AWS Single Sign-On (AWS SSO) Integration Guide for


This document helps you configure AWS SSO to facilitate single sign-on (SSO) for using SAML.



You’ll need the following to set up SSO access to

Setup instructions

  1. On the page in the AWS SSO Console, in the Details section, fill in the Display name, and the Description(optional) of the application.


We suggest that you choose a unique display name if you plan to have more than one of the same application.

  1. Log into your account as an administrator.

  2. Navigate to the Settings option on the left of the navigation bar and choose SSO.

  3. Insert these values under the Step 2 section.

  1. Download and copy the contents of the AWS SSO Certificate and paste its content into the Identity Provider's Certificate field.
  1. Choose Save Settings.

  2. Take note of the ACS URL / Consumer URL / Recipient and EntityID / Audience URI values as it is required later for the AWS SSO application configuration.

  3. Go back to the AWS SSO console page where you are configuring the Application.

  4. Under Application metadata, choose If you don't have a metadata file, you can manually type your metadata values. to display the application metadata settings.

  5. Insert these values you got from step 7:

Field Value
Application ACS URL ACS URL / Consumer URL / Recipient
Application SAML audience EntityID / Audience URI
  1. Click Save Changes.

  2. Assign a user to the application in AWS SSO.


Use the following sections to verify the SSO integration.


Ensure that the user performing the verification is logged out of both AWS SSO and the application before performing the steps in each section.

Verifying SSO from AWS SSO

  1. Access the AWS SSO end user portal using the credentials of a user assigned to the application.

  2. In the list of applications, choose to initiate a login to

  3. If login was successful you will be signed-in to the application.


If sign in was not successful, please see the troubleshooting steps.

Verifying Service Provider Initiated SSO from

  1. Access and enter the email address of a user assigned to the application in the AWS SSO console then choose Login.


Alternatively, you can also access the WAYFLess URL (optional) provided to you by and available in the console. WAYFLess URL also initiates the Service Provider (SP) initiated flow from

  1. You will be redirected to AWS SSO portal, type the credentials of user assigned to the application in the AWS SSO console.

  2. Choose Sign In.

  3. If login was successful you will be signed-in to the application.


If sign in was not successful, please see the troubleshooting steps.


Error Issue Solution
404 The ACS URL may be incorrect Review the Application ACS URL attribute configured in your AWS SSO if it matches the one provided from
"404 Resource not found" It's possible that Issuer URL from AWS is incorrect under the configuration Make sure that the URLs from AWS inserted under are correct.
"SAML Authentication Error. The Identity Provider's Certificate configured in the SSO Setup Form is incorrect" It's possible that the certificate inserted is incorrect Make sure that you have correctly inserted the AWS certificate under your configuration.
"SAML Authentication Error. While trying to check the signature of the assertion, the SAML library could not find an appropriate metadata entry for the Issuer specified in the SAML response." It's possible that the AWS SSO Issuer is incorrect Make sure that the URL for the EntityID inserted under is correct.
Other When AWS SSO creates a SAML Assertion for a user, it uses the value of the 'email' and 'subject' fields (if they are present) from the connected directory to populate the 'Email' and 'Subject' attributes in the SAML assertion. Many service providers expect these attributes to contain the user’s email address. By default your directory is configured to send 'windowsUPN' in both fields. Your directory may be configured to contain the users email in the 'Email' attribute instead. If so, you may need to change this in your Connected directory settings. Additionally the 'name' attribute being sent to the provider should not be the user's email address, make sure that your attribute name is not mapping to an email.

For general troubleshooting problems, please refer to Troubleshooting Guide.

User Provisioning Types

There are two user provisioning you need to aware of:

User Provisioning