Skip to main content


Configuring GravityZone Cloud single sign-on with Okta

GravityZone Cloud supports single sign-on (SSO) with various Identity Providers (IdP) that use SAML 2.0 as authentication standard.

This topic describes how to configure GravityZone Cloud single sign-on with Okta. For generic information on configuring other Identity Providers, refer to Configuring single sign-on using a 3rd party Identity Provider.

Prerequisites and requirements
  • You have an Okta account to create, activate and assign applications to users.

  • You have a GravityZone Cloud administrator account to manage users, your company and other companies.

  • GravityZone users have Okta accounts with the same email addresses.


  • As GravityZone administrator, you can configure single sign-on for users from your company and from companies under your management. You cannot enable SSO for your own GravityZone account due to security reasons.

  • Users must be under companies that have SSO enabled. While SSO is active, users cannot log in with GravityZone credentials.

  • Email addresses are case sensitive with GravityZone SSO. Therefore, username@company.domain is different from UserName@company.domain and USERNAME@company.domain. If the email address from GravityZone does not match the email address from the Identity Provider, the user will receive a login error message when trying to connect to Control Center.

Configure Okta

GravityZone single sign-on requires an Okta application that will connect the two platforms.

This is how you configure an Okta application:

  1. Log in to Okta.

  2. Go to the Admin section.

  3. Go to the Applications section and click Create App Integration.

  4. In the Create a new app integration window, select WebSAML 2.0 as sign-in method, and click Next.

  5. On the Create SAML Integration page, make the following configuration:

    1. Under General Settings, enter an app name (for example, GZ App), and click Next.

      Additionally, you can upload a logo image and set your app’s visibility.

    2. Under SAML Settings, fill in the following fields:

      • Single sign on URL. Enter and select the check box for Use this for Recipient URL and Destination URL.

      • Audience URL (SP Entity ID). Enter

      • Name ID format. Select Email Address.


        Click the Show Advanced Settings link for more options.

      • Response. Select Signed.

      • Assertion Signature. Select Signed.

      • Signature Algorithm. Select RSA-SHA256.

      • Digest Algorithm. Select SHA256.

      • Assertion Encryption. Select Unencrypted.

      • Enable Single Logout. Select the check box for Allow application to initiate Single Logout to display new options.

      • Single Logout URL. Enter

      • SP Issuer. Enter

      • Signature Certificate. Here you need to upload the GravityZone public certificate. For details on how to obtain this certificate, refer to Obtain the GravityZone public certificate.

      • Assertion Inline Hook. Select None (disabled).

      • Authentication context class. Select PasswordProtectedTransport.

      • Honor Force Authentication. Select Yes.

      • SAML Issuer ID. Leave the default value:${org.externalKey}


      Leave the rest of the fields blank, including Attribute Statements (optional) and Group Attribute Statements (optional).

    3. Click Next.


      Make sure you have entered all the above data and uploaded the GravityZone certificate before proceeding further.

    4. On the next page, select I'm an Okta customer adding an internal app and click Finish.

  6. After finishing the configuration, Okta will redirect you to a page containing details about the application you have created.

    In the Sign On tab, click the Identity Provider metadata link to view the XML file of the application.


    The URL of the page that displays the XML file is the one that you have to paste in GravityZoneControl Center to enable SSO. Copy the URL and keep it at hand for future use.

  7. Go to the Applications page in Okta to view the status of your application. The application must be active. Click the configuration button for assigning users, user groups, and for deactivating the application.

Obtain the GravityZone public certificate

This section describes how to obtain the GravityZone public certificate by using the Mozilla Firefox browser.

  1. Open the Firefox browser.

  2. Go to

  3. In the upper-side menu of the browser, click Tools and select Page Info.


    Alternately, click the lock icon in the address bar, then click the right arrow in the Site information drop-down menu. In the next panel, click More information.

  4. In the Page Info window, go to the Security tab and click the View Certificate button.

  5. On the certificate page, click PEM (cert) to download the certificate on your computer.


Go back to the SAML configuration page in Okta, upload the certificate and continue configuring the identity provider.

Enable SSO in GravityZone

After configuring single sign-on in Okta, to go to GravityZoneControl Center to enable SSO for companies and users. Only users under a company with SSO enabled have the option to log in with an Identity Provider.

Enable SSO for your company

This is how you enable SSO for your company:

  1. In the upper-right corner of Control Center, go to Welcome, [your username] > My Company.

  2. In the Authentication tab, under Single Sign on using SAML, enter the Identity Provider metadata URL in the corresponding field. The other field, reserved for the GravityZone metadata URL, is non-editable.

  3. Click Save.

Enable SSO for managed companies

This is how you enable single sign-on for a company under your management:

  1. Go to the Companies page.

  2. In the table, click the company’s name.

  3. Under Configure Single Sign-on using SAML, enter the Identity Provider metadata URL in the corresponding field. The other field, reserved for the GravityZone metadata URL, is non-editable.

  4. Click Save.

Change the authentication method for users

After enabling SSO for a company, GravityZone user accounts under that company become available for changing their authentication method.

You can change the authentication method for users one by one, as follows:

  1. Go to the Accounts page.

  2. In the table, click the user’s name.

  3. Under Settings and Privileges, go to Authentication method and select Login using your Identity Provider.

  4. Click Save.


    You can enable SSO for as many GravityZone users as you want, but not for your own administrator account.


    If the configuration page of a GravityZone user account does not display the Settings and Privileges section, then probably the company has not SSO enabled.

Test GravityZone SSO

After configuring both the identity provider and GravityZone, you can test single sign-on as follows:

  1. Log out from GravityZone.

  2. Log out from Okta.

  3. Go to


    GravityZone SSO does not support IdP initiated login, but only service provider initiated login. Therefore, you can test the single sign-on by going to the GravityZone console (Control Center), not by clicking the application's logo in Okta.

  4. Enter a valid email address created for testing (other than the one of your GravityZone administrator account).

  5. Click Next.

    You should be redirected to the Identity Provider's authentication page.

  6. Authenticate with your identity provider.

    You will be redirected back to GravityZone and, in a few moments, you should automatically log in to Control Center.

Disable GravityZone SSO

To disable single sign-on for your company or for a company under your management:

  1. Delete the Identity Provider metadata URL from the configuration page of that company.

  2. Click Save and confirm the action.

Users can obtain new passwords by clicking the Forgot password? link on the Control Center login page and following the instructions.

To re-enable GravityZone SSO for a company, enter again the Identity Provider in the configuration page and click Save.

After re-enabling SSO, users under that company will continue to log in to Control Center with GravityZone credentials. You have to manually configure each account, one by one, to log in with the Identity Provider again.