AWS SAML Integration
This document explains how to implement MonoSign with AWS. It covers Single Sign-On. Before you continue, it is better to start with AWS’s Single Sign-On implementation page.
View AWS SSO Metadata
In order to configure the SAML key on MonoSign for AWS SSO, you need to have various information provided by AWS. First, navigate to Services > Security, Identity, & Compliance > AWS Single Sign On and click Settings from the sidebar. In the Identity Source tab, click Actions > Change Identity Source.
![](../__attachments/4325377/CleanShot%202022-06-01%20at%2012.25.04%202.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
Choose External Identity Provider and click Next. You will see Service provider metadata like in the image below.
![](../__attachments/4325377/CleanShot%202022-06-01%20at%2012.32.56.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
For now, we will stop here on the AWS side and create a MonoSign application and related SAML key by using the information provided by AWS.
Creating an Application and Access Key on MonoSign
Create your application on MonoSign and make sure you typed AWS SSO Sign-in URL to URL input.
![](../__attachments/4325377/CleanShot%202022-06-01%20at%2012.53.40.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
Once you created the application and navigated to the detail page, click Keys and Add New Key to create a SAML access key.
![](../__attachments/4325377/CleanShot%202022-06-01%20at%2013.08.50.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
In the opened modal, choose SAML as Key Type and switch to SAML2 Settings. Fill in the necessary fields according to the information provided by AWS. Correspondings of the fields are as below.
Field | Value |
---|---|
Assertion Consumer Url | AWS SSO ACS URL from Service provider metadata |
Entity Id | AWS SSO Issuer URL from Service provider metadata |
NameId Format | urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress |
Name Id |
Click Save and you are gonna see your configuration for your access key as follows;
![](../__attachments/4325377/CleanShot%202022-06-09%20at%2012.01.22.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
Configuration Single Sign-On for AWS
We are gonna move on to where we left off on the AWS Identity Source Change page which is mentioned in the first chapter. Under the Service provider metadata, There is an Identity provider metadata form.
![](../__attachments/4325377/CleanShot%202022-06-01%20at%2017.00.10.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
Fill in the necessary fields according to the access key created on MonoSign. Correspondings of the fields are as below.
Field | Value |
---|---|
IdP sign-in URL | Sign On Service from the application SAML key |
IdP issuer URL | Entity Id from the application SAML key |
IdP certificate | The certificate issued to access key - can be downloadable from the key detail. |
Click Next. Review the information in the last step and click Change identity source. If no error occurs while processing, you will be redirected to the settings page.
For external identity providers, provisioning method turns in to Manual. Which means you need to have smiliar users assigned to desired AWS accounts.
![](../__attachments/4325377/CleanShot%202022-06-01%20at%2017.39.51.png?inst-v=866e9140-3da7-430a-a281-7dc8294ac19e)
You can check the identity provider and authentication protocol. If any error occurs while processing, please contact support.