Configure CloudGuard SSO with JumpCloud


Based on JumpCloud documentation

Single Sign-On (SSO) with JumpCloud

Prerequisites

To successfully complete the integration between JumpCloud and CloudGuard, you must use an owner account in CloudGuard.

Notes:

  1. CloudGuard does not support automatic new user provisioning via SSOClosed Single Sign-On (SSO) - A session/user authentication process that permits a user to enter one name and password in order to access multiple applications.. Prior to attempting SSO, all users must have a CloudGuard account that uses the same email as their JumpCloud account.

  2. To prevent account lockout, CloudGuard does not allow the account owner to use single sign-on.

  3. This instruction assumes that the JumpCloud administrator that performs the integrations understands the process of generating private keys in addition to public certificates. See below the generation of signed certificates on Linux as an example. For generation of keys on other operating systems, refer to these operating systems documentation.

    • Create a private key opensslgenrsa -out private.pem 2048

    • Create a public certificate for that private key:

      opensslreq -new -x509 -key private.pem -out cert.pem -days 1095

To restrict access to a smaller group of users:

  1. Notice the IdP URL name for this app in the Application details, for example, https://sso.jumpcloud.com/saml2/ ConnectorName.

  2. Create a new Tag and name it SSO-ConnectorName. Important: This tag name is case sensitive.

  3. Add users to this Tag who should be given access to CloudGuard via Single Sign-On. Any other users who are not in this tag will be denied access.

    Important - If the Tag does not exist, all users in your organization will be authorized to access CloudGuard.

Test the SSO Configuration