Integrate with Amazon Business

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. Yada yada.

Read this article to learn how to integrate with Amazon Business. 

Prerequisites

• JumpCloud SSO Package or higher or SSO à la carte option
• JumpCloud configured as an IdP in Amazon
• A JumpCloud security group for use as the default Amazon Buying Group in SSO.
• An Amazon Business account
• Your Amazon Business ID

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. Replace any instances of YOUR_ID with your Amazon Business ID.
4. Add or change any desired attributes.
5. Click save.

Creating a new JumpCloud Application Integration

1. Log in to the JumpCloud Admin Portal.
2. Navigate 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.

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

Copy the metadata URL

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 Copy Metadata URL.
3. The URL will be copied to your clipboard.

To configure Amazon Business

1. Sign in to your up Amazon Business company site as an administrator
2. Navigate to User Profile > Business Settings.
3. On the System integrations wizard, select Single Sign-On (SSO).
4. On the Set up SSO wizard, select JumpCloud and click Next.
5. On the New user account defaults wizard, select your Default Group and Default Buying Role according your Organization needs.
6. Click Next.
7. On the Upload your metadata file wizard, select Paste XML Link and paste the JumpCloud Metadata URL copied in the previous section.
8. Click Validate.
9. When the metadata URL populates the fields in the Connection data section, click Next.
10. Skip the Upload your Attribute statement wizard.
11. On the Attribute mapping wizard, add the requirement fields by clicking the + Add a field option. Add the attribute values including the namespace, which you can copy from the USER ATTRIBUTE MAPPING section of the JumpCloud Admin portal into the SAML AttributeName fields.
12. Click Next.
13. On the Amazon connection data wizard, select I confirm that Amazon’s metadata has been configured on my IDP.
14. Click Continue.
15. Check the Status of the steps which have been configured and if they are green, click Start testing.
16. On the Test SSO Connection wizard, click Test.
17. On the IDP initiated URL wizard, before you click Activate, copy the value which is assigned to idpid and paste into the idpid parameter in the Reply URL in the Basic SAML Configuration section.
18. On the Are you ready to switch to active SSO? wizard, check I have fully tested SSO and am ready to go live checkbox and click on Switch to active.
19. Finally in the SSO Connection details section the Status is shown as Active.

Using JIT Provisioning

Additional attributes are required to use JIT provisioning. JIT required attributes are prepopulated and are on by default to enable JIT provisioning. You can’t edit the JIT required service provider attributes. You can customize the JumpCloud attribute name and the constant value for JIT required attributes. Toggle off the attributes to opt out of sending the attributes in the SAML assertion

To complete the provisioning process

1. Authorize a user’s access to the application in JumpCloud.  
2. Have the user log in to the application using SSO. The SAML assertion passes from JumpCloud to the service provider, and gives the service provider the information it needs to create the user account.

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 authentication workflow(s)

IdP Initiated

• Access the JumpCloud User Console.
• Select the application’s tile.
• The application will launch and login the user.

SP Initiated

• Navigate to your Service Provider application URL.
• You will be redirected to log in to the JumpCloud User Portal.
• The browser will be redirected back to the application and be automatically logged in.

Removing the SSO Integration

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.