Integrate with AWS Client VPN

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 Client VPN connector. 

Prerequisites

  • A JumpCloud administrator account.
  • JumpCloud SSO Package or higher or SSO add-on feature.
  • AWS Admin account (AWS root user)
  • AWS organization
  • An Amazon VPC with an EC2 instance is required.
  • You need a private certificate imported into AWS Certificate Manager (ACM).
  • You need a Windows or Mac system running the latest AWS Client VPN software.
    • You can download the software here.

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. The SP Entity ID should be urn:amazon:webservices:clientvpn.
  4. The ACS URL should be http://127.0.0.1:35001.
  5. In the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  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

Configure JumpCloud as an AWS Identity Provider

  1. Log in to the Amazon Web Services 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 left hand side nav, select Identity Providers.
  4. Select Create Provider.
  5. For Provider Type, select SAML.
  6. For Provider Name, 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, then upload the metadata file.

Note:

By default, the JumpCloud metadata file is saved as JumpCloud-aws-metadata.xml.

  1. Select Next Step.
  2. On the next screen, select Create.

Create an AWS Client VPN Endpoint

After you set up JumpCloud as the identity provider in AWS, create an AWS Client VPN Endpoint.

  1. Log in to the Amazon Web Services console for your organization as an administrator.
  2. In the Find Services search bar, enter VPC, then select VPC from the results. 
  3. One the left hand side nav, select Client VPN Endpoints under Virtual Private Network (VPN)
  4. Click Create Client VPN Endpoint
  5. Enter information for Name Tag and Description.
  6. To allocate an IP range for your remote users, enter the IP range In Client IPv4 CIDR
  7. For Server Certificate ARN, select the certificate you created. See Prerequisites
  8. For Authentication Options, select Use user-based authentication, then Federated authentication
  9. For SAML provider ARN, select JumpCloud, the identity provider you created in Configure JumpCloud as an AWS Identity Provider.
  10. To log connections in Amazon CloudWatch, select Yes for Do you want to log the details on client connections?.  If you don’t want to log connections, select No
  11. To ensure that only the traffic to the VCP IP range is forwarded using the VPN,  select the check box for Enable split-tunnel
  12. Click Create Client VPN Endpoint

Configure AWS Client VPN Endpoint Options

Finish configuring your AWS Client VPN endpoint by associating it with a target VPC and setting up SAML group-specific authorization. 

To associate a Client VPN with a Target VPC
  1. Log in to the Amazon Web Services console for your organization as an administrator.
  2. In the Find Services search bar, enter VPC, then select VPC from the results. 
  3. One the left hand side nav, select Client VPN Endpoints under Virtual Private Network (VPN)
  4. Select the Client VPN endpoint created in Create an AWS Client VPN Endpoint. It’s in a Pending state. 
  5. Select Associations, then click Associate.
  6. From the drop-down, select the target VPC and subnet you want to associate your endpoint with.
  7. (Optional) Repeat the previous steps to associate your Client VPN endpoint to another subnet for high availability.
To set up SAML group-specific authorization
  1. Select Authorization in the Client VPN options, then click Authorize Ingress.
  2. For Destination network to enable, enter the IP address of your EC2 instance created in the prerequisites.
  3. For Grant access to, select Allow access to users in a specific access group.
  4. For Access group ID field, enter the name of the group you want to allow access to the EC2 instance. 
  5. Optionally, provide a description. 
  6. Click Add authorization rule.

Testing the AWS VPN Client Connection

To verify you configured your AWS VPN Client correctly, test connecting to the AWS VPN client. 

To test connecting to the AWS VPN client

  1. Log in to the Amazon Web Services console for your organization as an administrator.
  2. In the Find Services search bar, enter VPC, then select VPC from the results. 
  3. One the left hand side nav, select Client VPN Endpoints under Virtual Private Network (VPN)
  4. Select the Client VPN endpoint you configured in Configure AWS Client VPN Endpoint Options. It’s in an Active state. 
  5. To download the configuration profile to your desktop, click Download Client Configuration.
  6. Open the AWS Client VPN desktop app on your system. See Prerequisites.
  7. In the menu, go to File > Manage Profiles.
  8. Click Add Profile and select the configuration profile you downloaded in step 2. Give it a display name. 
  9. You see the profile in the AWS Client VPN list. Select it, then click Connect.

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.

Authentication workflow

  1. The user opens the AWS provided client on their device and initiates a connection to the Client VPN endpoint.
  2. The Client VPN endpoint sends an IdP URL and authentication request back to the client, based on the information that was provided in the IAM SAML identity provider.
  3. The AWS provided client opens a new browser window on the user’s device. The browser makes a request to the IdP and displays a login page.
  4. The user enters their credentials on the login page, and the IdP sends a signed SAML assertion back to the client.
  5. The AWS provided client sends the SAML assertion to the Client VPN endpoint.
  6. The Client VPN endpoint validates the assertion and either allows or denies access to the user.

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