- \n
- A JumpCloud administrator account<\/li>\n\n\n\n
- JumpCloud SSO Package or higher or SSO \u00e0 la carte option<\/li>\n\n\n\n
- AWS Admin account (AWS root user)<\/li>\n\n\n\n
- AWS organization<\/li>\n\n\n\n
- Your\u00a0AWS Account number<\/strong><\/li>\n<\/ul>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\")
<\/p><\/div>Tip:<\/strong> \nFind your account number by going to the main AWS console, go to\u00a0All Services<\/strong>, under\u00a0Security, Identity & Compliance<\/strong>\u00a0select\u00a0IAM<\/strong>. It will be embedded in the IAM users sign-in link:\u00a0https:\/\/YOUR_AWS_ACCOUNT_NUMBER.signin.aws.amazon.com\/console<\/kbd>.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Important Considerations<\/strong><\/p>\n\n\n\n
- \n
- Amazon IAM accepts SSO based on roles. Enabling SSO for Amazon AWS (IAM) in this way will allow any user in your organization to access Amazon AWS GovCloud (IAM). Multiple Roles may be defined as detailed below<\/em>.<\/li>\n\n\n\n
- This connector supports additional Constant Attributes that are sent in the assertion. E.g., Amazon supports SessionDuration<\/a> in order to allow up to 12 hour sessions before logout. By default, the connector template contains this additional attribute where the Name is https:\/\/aws.amazon.com\/SAML\/Attributes\/SessionDuration<\/kbd> and the Value in seconds must be between 15 minutes and 12 hours; e.g., for 15 minutes, enter a value of 900.<\/li>\n<\/ul>\n\n\n\n
Creating a new JumpCloud Application Integration<\/strong><\/h2>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to\u00a0USER AUTHENTICATION\u00a0<\/strong>>\u00a0SSO<\/strong> Applications<\/strong>.<\/li>\n\n\n\n
- Click + Add New Application<\/strong>.<\/li>\n\n\n\n
- Type the name of the application in the Search <\/strong>field and select it.<\/li>\n\n\n\n
- Click Next<\/strong>.<\/li>\n\n\n\n
- In the Display Label<\/strong>, type your name for the application. Optionally, you can enter a Description<\/strong>, adjust the User Portal Image and choose to hide or Show in User Portal<\/strong>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\")
<\/p><\/div>Note:<\/strong> \nIf this is a Bookmark Application, enter your sign-in URL in the Bookmark URL<\/strong> field.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Optionally, expand Advanced Settings<\/strong> to specify a value for the SSO IdP URL<\/strong>. If no value is entered, it will default to https:\/\/sso.jumpcloud.com\/saml2\/<applicationname><\/kbd>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>Warning:<\/strong> \nThe SSO IdP URL<\/strong> is not editable after the application is created. You will have to delete and recreate the connector if you need to edit this field at a later time.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Click Save Application<\/strong>.<\/li>\n\n\n\n
- If successful, click:\n
- \n
- Configure Application<\/strong> and go to the next section <\/li>\n\n\n\n
- Close<\/strong> to configure your new application at a later time <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
Configuring the SSO Integration<\/strong><\/h2>\n\n\n\n
To configure JumpCloud<\/strong><\/h3>\n\n\n\n
- \n
- Create a new application<\/a> or select it from the Configured Application<\/strong>s list.<\/li>\n\n\n\n
- Select the SSO <\/strong>tab.<\/li>\n\n\n\n
- Configure one or more Roles:\n
- \n
- Under Constant Attributes<\/strong>, in the second row containing NAME<\/strong> https:\/\/aws.amazon.com\/SAML\/Attributes\/Role<\/kbd>, update the Value<\/strong> by replacing YOUR_AWS_ACCOUNT_NUMBER with your actual AWS Account number. This is done twice in the field. You may want to copy\/paste it from a text document. arn:aws-us-gov:iam::YOUR_AWS_ACCOUNT_NUMBER:role\/ROLE_1,arn:aws-us-gov:iam::YOUR_AWS_ACCOUNT_NUMBER:saml-provider\/JumpCloud<\/kbd><\/li>\n\n\n\n
- Replace ROLE_1 with the role created using the steps under To configure AWS GovCloud.<\/strong><\/li>\n\n\n\n
- Create as many role attributes as desired by using the same NAME<\/strong> and a VALUE<\/strong> with a unique role<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- In the field terminating the IdP URL<\/strong>, either leave the default value or enter a plaintext string unique to this connector.<\/li>\n\n\n\n
- (Optional) In the Display Label<\/strong> field, enter a label that will appear beside the Amazon Web Services Govcloud IAM logo within the JumpCloud console to guide administrators and users to the connection you have configured.<\/li>\n\n\n\n
- Click save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
Download the JumpCloud metadata<\/strong> file<\/strong><\/h4>\n\n\n\n
- \n
- Find your application in the Configured Applications<\/strong> list and click anywhere in the row to reopen its configuration window.<\/li>\n\n\n\n
- Select the SSO <\/strong>tab and click Export Metadata<\/strong>.<\/li>\n\n\n\n
- The JumpCloud-<applicationname>-metadata.xml<\/strong> will be exported to your local Downloads <\/strong>folder.<\/li>\n<\/ol>\n\n\n\n
<\/p><\/div>Tip:<\/strong> \nMetadata can also be downloaded from the Configured Applications<\/strong> list. Search for and select the application in the list and then click Export Metadata<\/strong> in the top right corner of the window.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
To configure AWS GovCloud (US)<\/strong><\/h3>\n\n\n\n
- \n
- Log in to the Amazon Web Services GovCloud console for your organization as an administrator.<\/li>\n\n\n\n
- In the main console, go to All Services<\/strong>, under Security, Identity & Compliance<\/strong> select IAM.<\/strong><\/li>\n\n\n\n
- On the lefthand sidenav, select on Identity Providers.<\/strong><\/li>\n\n\n\n
- Select Create Provider.<\/strong><\/li>\n\n\n\n
- In the Provider Type<\/strong> drop-down, select SAML.<\/strong><\/li>\n\n\n\n
- In the Provider Name<\/strong> field, enter JumpCloud<\/kbd>. If another name is chosen, this string will need to replace JumpCloud <\/kbd>in the role attribute value in the JumpCloud configuration.<\/li>\n\n\n\n
- Select Choose File<\/strong> and upload the metadata file, by default, it will be saved as JumpCloud-awsgov-metadata.xml.<\/li>\n\n\n\n
- Select Next Step.<\/strong><\/li>\n\n\n\n
- On the next screen, select Create.<\/strong><\/li>\n\n\n\n
- In the lefthand side-nav, select Roles.<\/strong><\/li>\n\n\n\n
- Select Create role.<\/strong><\/li>\n\n\n\n
- For Select type of trusted entity<\/strong>, select SAML<\/li>\n\n\n\n
- For SAML Provider<\/strong>, select the provider created in the steps above.<\/li>\n\n\n\n
- Select Allow programmatic and AWS Management Console access<\/strong>. Select Next: Permissions<\/strong>.<\/li>\n\n\n\n
- Attach the desired permission policy for the role. Select Next: Review<\/strong><\/li>\n\n\n\n
- Define a Role Name<\/strong>. This string replaces ROLE_1 in the JumpCloud configuration<\/li>\n\n\n\n
- Select Create role<\/strong>.<\/li>\n<\/ol>\n\n\n\n
Authorizing User SSO Access<\/strong><\/h2>\n\n\n\n
Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Application Configuration<\/strong> panel or from the Groups Configuration<\/strong> panel. <\/p>\n\n\n\n
To authorize user access from the Application Configuration panel<\/strong><\/h3>\n\n\n\n
- \n
- Log in to the <\/a>JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to USER AUTHENTICATION > SSO<\/strong> Applications<\/strong>, then select the application to which you want to authorize user access.<\/li>\n\n\n\n
- Select the User Groups<\/strong> tab. If you need to create a new group of users, see Get Started: User Groups<\/a>.<\/li>\n\n\n\n
- Select the check box next to the group of users you want to give access.<\/li>\n\n\n\n
- Click save<\/strong>. <\/li>\n<\/ol>\n\n\n\n
To learn how to authorize user access from the Groups Configuration<\/strong> panel, see Authorize Users to an SSO Application<\/a>.<\/p>\n\n\n\n
Validating SSO user authentication workflow(s)<\/strong><\/h2>\n\n\n\n
IdP-initiated<\/strong> user workflow<\/strong><\/h3>\n\n\n\n
- \n
- Access the JumpCloud User Console<\/a><\/li>\n\n\n\n
- Go to\u00a0Applications<\/strong> and click an application tile to launch it<\/li>\n\n\n\n
- JumpCloud asserts the user’s identity to the SP and is authenticated without the user having to log in to the application<\/li>\n<\/ul>\n\n\n\n
SP-initiated<\/strong> user workflow<\/strong><\/h3>\n\n\n\n
- \n
- Go\u00a0to the SP application login – generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO<\/li>\n<\/ul>\n\n\n\n<\/p><\/div>Note:<\/strong> \n
This varies by SP.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Login redirects the user to JumpCloud where the user enters their JumpCloud credentials<\/li>\n\n\n\n
- After the user is logged in successfully, they are redirected\u00a0back to the SP and automatically logged in<\/li>\n<\/ul>\n\n\n\n
Removing the SSO Integration<\/strong><\/h2>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\")
<\/p><\/div>Important:<\/strong> \nThese are steps for removing the integration in JumpCloud. Consult your SP’s documentation for any additional steps needed to remove the integration in the SP. Failure to remove the integration successfully for both the SP and JumpCloud may result in users losing access to the application.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
To deactivate<\/strong><\/strong> the SSO Integration<\/strong><\/h3>\n\n\n\n
- Go to\u00a0Applications<\/strong> and click an application tile to launch it<\/li>\n\n\n\n
- Go to USER AUTHENTICATION > SSO<\/strong> Applications<\/strong>, then select the application to which you want to authorize user access.<\/li>\n\n\n\n
- On the lefthand sidenav, select on Identity Providers.<\/strong><\/li>\n\n\n\n
- Select the SSO <\/strong>tab and click Export Metadata<\/strong>.<\/li>\n\n\n\n
- Replace ROLE_1 with the role created using the steps under To configure AWS GovCloud.<\/strong><\/li>\n\n\n\n
- Select the SSO <\/strong>tab.<\/li>\n\n\n\n
- Close<\/strong> to configure your new application at a later time <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
- If successful, click:\n
- Click Save Application<\/strong>.<\/li>\n\n\n\n
- Go to\u00a0USER AUTHENTICATION\u00a0<\/strong>>\u00a0SSO<\/strong> Applications<\/strong>.<\/li>\n\n\n\n
- This connector supports additional Constant Attributes that are sent in the assertion. E.g., Amazon supports SessionDuration<\/a> in order to allow up to 12 hour sessions before logout. By default, the connector template contains this additional attribute where the Name is https:\/\/aws.amazon.com\/SAML\/Attributes\/SessionDuration<\/kbd> and the Value in seconds must be between 15 minutes and 12 hours; e.g., for 15 minutes, enter a value of 900.<\/li>\n<\/ul>\n\n\n\n
- Amazon IAM accepts SSO based on roles. Enabling SSO for Amazon AWS (IAM) in this way will allow any user in your organization to access Amazon AWS GovCloud (IAM). Multiple Roles may be defined as detailed below<\/em>.<\/li>\n\n\n\n