Integrate with AWS GovCloud (US)

Use JumpCloud SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials.

Read this article to learn how to configure the AWS GovCloud connector. 

Prerequisites

  • A JumpCloud administrator account
  • JumpCloud SSO Package or higher or SSO à la carte option
  • AWS Admin account (AWS root user)
  • AWS organization
  • Your AWS Account number

Tip:

Find your account number by going to the main AWS console, go to All Services, under Security, Identity & Compliance select IAM. It will be embedded in the IAM users sign-in link: https://YOUR_AWS_ACCOUNT_NUMBER.signin.aws.amazon.com/console.

Important Considerations

  • 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.
  • This connector supports additional Constant Attributes that are sent in the assertion. E.g., Amazon supports SessionDuration 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 and the Value in seconds must be between 15 minutes and 12 hours; e.g., for 15 minutes, enter a value of 900.

Creating a new JumpCloud Application Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION SSO Applications.
  3. Click + Add New Application.
  4. Type the name of the application in the Search field and select it.
  5. Click Next.
  6. In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.

Note:

If this is a Bookmark Application, enter your sign-in URL in the Bookmark URL field.

  1. Optionally, expand Advanced Settings to specify a value for the SSO IdP URL. If no value is entered, it will default to https://sso.jumpcloud.com/saml2/<applicationname>.

Warning:

The SSO IdP URL 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.

  1. Click Save Application.
  2. If successful, click:
    • Configure Application and go to the next section
    • Close to configure your new application at a later time

Configuring the SSO Integration

To configure JumpCloud

  1. Create a new application or select it from the Configured Applications list.
  2. Select the SSO tab.
  3. Configure one or more Roles:
    • Under Constant Attributes, in the second row containing NAME https://aws.amazon.com/SAML/Attributes/Role, update the Value 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
    • Replace ROLE_1 with the role created using the steps under To configure AWS GovCloud.
    • Create as many role attributes as desired by using the same NAME and a VALUE with a unique role
  4. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  5. (Optional) In the Display Label 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.
  6. Click save.

Download the JumpCloud metadata file

  1. Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
  2. Select the SSO tab and click Export Metadata.
  3. The JumpCloud-<applicationname>-metadata.xml will be exported to your local Downloads folder.

Tip:

Metadata can also be downloaded from the Configured Applications list. Search for and select the application in the list and then click Export Metadata in the top right corner of the window.

To configure AWS GovCloud (US)

  1. Log in to the Amazon Web Services GovCloud console for your organization as an administrator.
  2. In the main console, go to All Services, under Security, Identity & Compliance select IAM.
  3. On the lefthand sidenav, select on Identity Providers.
  4. Select Create Provider.
  5. In the Provider Type drop-down, select SAML.
  6. In the Provider Name field, enter JumpCloud. If another name is chosen, this string will need to replace JumpCloud in the role attribute value in the JumpCloud configuration.
  7. Select Choose File and upload the metadata file, by default, it will be saved as JumpCloud-awsgov-metadata.xml.
  8. Select Next Step.
  9. On the next screen, select Create.
  10. In the lefthand side-nav, select Roles.
  11. Select Create role.
  12. For Select type of trusted entity, select SAML
  13. For SAML Provider, select the provider created in the steps above.
  14. Select Allow programmatic and AWS Management Console access. Select Next: Permissions.
  15. Attach the desired permission policy for the role. Select Next: Review
  16. Define a Role Name. This string replaces ROLE_1 in the JumpCloud configuration
  17. Select Create role.

Authorizing User SSO Access

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 panel or from the Groups Configuration panel. 

To authorize user access from the Application Configuration panel

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
  3. Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
  4. Select the check box next to the group of users you want to give access.
  5. Click save

To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.

Validating SSO user authentication workflow(s)

IdP-initiated user workflow

  • Access the JumpCloud User Console
  • Go to Applications and click an application tile to launch it
  • JumpCloud asserts the user’s identity to the SP and is authenticated without the user having to log in to the application

SP-initiated user workflow

  • Go to the SP application login – generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO

Note:

This varies by SP.

  • Login redirects the user to JumpCloud where the user enters their JumpCloud credentials
  • After the user is logged in successfully, they are redirected back to the SP and automatically logged in

Removing the SSO Integration

Important:

These 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.

To deactivate the SSO Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Select the SSO tab.
  5. Scroll to the bottom of the configuration.
  6. Click Deactivate SSO
  7. Click save
  8. If successful, you will receive a confirmation message.

To delete the application

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to delete.
  4. Check the box next to the application to select it.
  5. Click Delete.
  6. Enter the number of the applications you are deleting
  7. Click Delete Application.
  8. If successful, you will see an application deletion confirmation notification.
Back to Top

List IconIn this Article

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case