- A public certificate and private key pair are required to successfully connect applications with JumpCloud. After you activate an application, we automatically generate a public certificate and private key pair for you. You can use this pair or upload your own.
- In order to successfully complete the integration between JumpCloud and NetSuite, you must use an administrator account in NetSuite.
- After you connect an application to JumpCloud, you can connect it to user groups. Users in the groups you connect can access the application through SAML SSO. Learn how to connect user groups to applications.
To configure JumpCloud SSO for NetSuite, you will need your NetSuite Account Number (ID). Follow the steps below to locate it:
- Log into your NetSuite account.
- Select Setup.
- Select Integration.
- In the Manage Integration section, select Web Services Preferences.
- You should see your Account ID Number.
Before users can authenticate using SSO, the NetSuite account administrator needs to add the "SAML Single Sign-on" permission to the appropriate roles. This can be done either by adding the permission to existing roles or by creating a new role with the SAML SSO permission and assigning that role to certain users. The administrator also has the option to add the “Set Up SAML Single Sign-on” permission to roles/users.
Configure the JumpCloud SSO Application
- Access the JumpCloud Administrator Console at https://console.jumpcloud.com.
- Select Applications in the main navigation panel.
- Select the + in the upper left, scroll or search for the application in the 'Configure New Application' side panel, the select 'configure'.
- You can upload a service provider application's XML metadata file to populate SAML connector attributes for that application. The attributes populated by the metadata file may vary by the application. To apply a metadata file for the application you're connecting, click Upload Metadata. Navigate to the file you want to upload, then click Open. You'll see a confirmation of a successful upload. Be aware that if you upload more than one metadata file, you'll overwrite the attribute values applied in the previously uploaded file.
- In the IDP Entity ID field, enter
- In the ACS URL field, enter
https://INSTANCE.netsuite.com/saml2/acs(replace INSTANCE with your NetSuite Instance: system.na1, system.na2, system.sandbox, etc.).
- In the Account Number field, enter
account=ACCOUNT_NUMBER(replace ACCOUNT_NUMBER with your NetSuite Account Number).
- In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
- (Optional) In the Display Label field, enter a label that will appear under the Service Provider logo within the JumpCloud User console.
- Select Activate.
- Select export metadata for NetSuite on the right-hand side of the page.
Configure the Service Provider
- Log in to NetSuite as an administrator.
- Select on the Setup tab and select Company from the drop-down menu.
- Select Enable Features.
- Select on the SuiteCloud tab.
- Check the box next to SAML Single Sign-on.
- Select on the Setup tab and select Integration from the drop-down menu.
- Select SAML Single Sign-On.
- In the Logout Landing Page field, enter
- In the Identity Provider Login Page field, enter the same IdP URL that you set in the JumpCloud console (if you did not modify the termination of this URL, then enter the default URL:
- Check the box next to Primary Authentication Method.
- Select Upload IdP Metadata File and upload the metadata file you downloaded from the JumpCloud console.
- Select Submit.
- Ensure that the appropriate roles are permitted to use SAML Single Sign-on.
Validate SSO authentication workflows
- Access the JumpCloud User Console at https://console.jumpcloud.com.
- Select the Service Provider icon.
- This should automatically launch and login to the application.
- 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.