

# AWS IAM Identity Center Integration Guide for 10000ft

## Introduction
<a name="app-0eb600b420aaa73f.introduction"></a>

Use this guide to configure IAM Identity Center for single sign-on (SSO) with 10000ft using SAML.

## Prerequisites
<a name="app-0eb600b420aaa73f.prerequisites"></a>

You’ll need the following to set up SSO access to 10000ft:
+ Access to the IAM Identity Center console with permissions to manage applications.
+ A 10000ft account with user permissions to configure **SAML SSO**.

 ​

## Setup instructions
<a name="app-0eb600b420aaa73f.setup-instructions"></a>

1. On the IAM Identity Center Configure page, in the **Details** section, fill in the **Display name** and the **Description**(optional) of the application.
**Note**  
We suggest that you choose a unique display name if you plan to have more than one of the same application.

1. Login to your 10000ft account as an administrator.(example: https://app.10000ft.com/si)

1. In the top right navigation panel, find **My Preferences**.

1. On the **SSO** page, choose **Edit**.

1. Insert these values:

   Use the **IAM Identity Center sign-in URL** shown in the IAM Identity Center metadata section on this application's configuration page in the IAM Identity Center console.

   Use the **IAM Identity Center sign-out URL** shown in the IAM Identity Center metadata section on this application's configuration page in the IAM Identity Center console.

1. Download and upload the **IAM Identity Center certificate**.

   Download the **IAM Identity Center certificate** from the IAM Identity Center metadata section on this application's configuration page in the IAM Identity Center console.

1. Choose **Save**.

1. Return to the **IAM Identity Center** console page where you are configuring the Application.

1. Under **Application metadata**, choose **specify configuration values individually** to display the application metadata settings.

1. Insert these values:  
**Application ACS URL**  
https://app.10000ft.com/saml/acs  
**Application SAML audience**  
https://app.10000ft.com/saml/metadata

1. Choose **Save Changes**.

1. [Assign a user to the application](https://docs.aws.amazon.com/singlesignon/latest/userguide/assignuserstoapp.html) in IAM Identity Center.

## Verification
<a name="app-0eb600b420aaa73f.verification"></a>

Use the following sections to verify the SSO integration.

**Note**  
Ensure that the user performing the verification is logged out of both IAM Identity Center and the application before performing the steps in each section.

### Verifying SSO from IAM Identity Center
<a name="app-0eb600b420aaa73f.verifying-sso-from-iam-identity-center"></a>

1. Access the AWS access portal using the credentials of a user assigned to the **10000ft** application.

1. In the list of applications, choose **10000ft** to initiate a login to 10000ft.

1. If login was successful you will be signed-in to the 10000ft application.

If sign in was not successful, see the [troubleshooting](#app-0eb600b420aaa73f.troubleshooting) steps.

### Verifying Service Provider Initiated SSO from 10000ft
<a name="app-0eb600b420aaa73f.verifying-service-provider-initiated-sso-from-10000ft"></a>

1. Access https://app.10000ft.com/si

1. Type the credentials of a user assigned to the application in the IAM Identity Center console.

1. Select **Sign in with your company account**

1. You will be redirected to IAM Identity Center portal, type the credentials of a user assigned to the application in the IAM Identity Center console.

1. You will be signed-in to the 10000ft web console if login was successful.

If sign in was not successful, see the [troubleshooting](#app-0eb600b420aaa73f.troubleshooting) steps.

## Troubleshooting
<a name="app-0eb600b420aaa73f.troubleshooting"></a>

**Error:** `"No Single Sign-on integration could be found."`

The **Application ACS URL** specified in the identity provider is incorrect.

Make sure that the 10000ft ACS URL is specified correctly in IAM Identity Center.

**Error:** `Other`

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

For general troubleshooting problems, see [Troubleshooting Guide](https://docs.aws.amazon.com/singlesignon/latest/userguide/troubleshooting.html).

### User Provisioning Types
<a name="app-0eb600b420aaa73f.user-provisioning-types"></a>

There are two types of user provisioning:
+ **Preprovisioned users** Preprovisioned users are users who must already exist in the downstream SaaS application. For instance, you may need to create SaaS users with the same subject as the AD users.
+ **JIT users** JIT (Just-In-Time) users do not necessarily exist in the downstream SaaS application, and are provisioned, created, or registered the first time the user federates. You may need to enable JIT option in your SaaS application for the AD domain.

## Learn more
<a name="app-0eb600b420aaa73f.learn-more"></a>

[Assign a user to the application](https://docs.aws.amazon.com/singlesignon/latest/userguide/assignuserstoapp.html?icmpid=docs_sso_app_setup)

[Troubleshooting Guide](https://docs.aws.amazon.com/singlesignon/latest/userguide/troubleshooting.html?icmpid=docs_sso_app_setup)