Configure JumpCloud SSO for SentinelOne Console Access

Overview

Stop sharing the admin@netnxt.com password. Use JumpCloud SSO to let your technicians log in to the SentinelOne Console using their own credentials.

Step 1: Configure JumpCloud (IdP)

Go to SSO Applications > (+) Add New.
Search for SentinelOne.
IdP Entity ID: JumpCloud
IdP URL: (Copy the Login URL provided).
Attributes: Ensure email maps to email.
Download Certificate: Save the public certificate.

Step 2: Configure SentinelOne (SP)

Log in to SentinelOne > Settings > Users > SSO.
Enable SSO: Toggle On.
IdP Issuer URL: Paste the JumpCloud Entity ID.
SAML Login URL: Paste the JumpCloud Login URL.
Certificate: Upload the certificate you downloaded in Step 1.
Save.

Step 3: Test

Assign the SentinelOne app to your "IT Admins" group in JumpCloud. Have a tech try to log in via the JumpCloud User Portal.

FAQ

1) How does JumpCloud SSO improve SentinelOne console security?

JumpCloud SSO replaces shared admin credentials by enforcing individual user authentication, improving auditability, access control, and reducing credential compromise risks.

2) What SAML attributes are required for SentinelOne SSO with JumpCloud?

The primary required attribute is the user email address, which must map correctly between JumpCloud and SentinelOne for successful SSO authentication.

3) Do you need to disable local SentinelOne accounts after enabling SSO?

It is recommended to restrict or limit local accounts after SSO is verified to ensure administrators authenticate only through JumpCloud-managed identities.

4) How do you test JumpCloud SSO integration with SentinelOne?

Assign the SentinelOne application to an IT admin group in JumpCloud and attempt login via the JumpCloud User Portal to validate successful SSO authentication.

5) Can JumpCloud SSO be limited to specific SentinelOne admin roles?

Yes, access can be controlled by assigning the SentinelOne SSO app only to specific JumpCloud user groups aligned with admin responsibilities.