Directly contact our Support Team

Configure GravityZone Cloud single sign-on with AD FS

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

This article explains how to configure an Active Directory Federation Services (AD FS) server as identity provider for GravityZone SSO. For other identity providers, refer to this article.

AD FS is a service provided by Microsoft as a standard role for Windows Server. Installing AD FS is beyond the scope of this article, so for details on this topic refer to this Microsoft KB article. When using SSO, it is useful to check the AD FS logs in the Windows Event Viewer for error details.

Prerequisites and requirements

  • You have a GravityZone Cloud administrator account to manage users, your company and other companies.
  • An Active Directory instance has been configured, where users have accounts with the same email addresses as in GravityZone.
  • AD FS service has been fully installed and configured.
  • You have a valid SSL certificate for AD FS and the fingerprint for that certificate.
important Important:
  • 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.

Configuring AD FS

To configure AD FS for single sign-on, you need to do the following:

  1. Add a relying party trust
  2. Create claim rules

Adding a relying party trust

The connection between GravityZone and ADFS is defined using a relying party trust.

  1. Log in to the server where AD FS is installed.
  2. Launch the AD FS Management application.
  3. Select Trust Relationships > Relying Party Trusts.
  4. Right-click and select Add Relying Party Trust….
  5. In the Add Relying Party Trust Wizard window, follow these steps:
    1. On the Welcome page, click Start.
    2. On the Select Data Source page:
      1. Select the option Import data about the relying party published online or on a local network.
      2. In the Federation metadata address (host name or URL) box, enter the address of the service provider: https://gravityzone.bitdefender.com/sp/metadata.xml
      3. Click Next.
    3. On the Specify Display Name page, enter the name of the service provider (gravityzone.bitdefender.com) and click Next.
    4. On the Configure Multi-factor Authentication Now? page, select the option I do not want to configure multi-factor authentication settings for this relying party trust at this time and click Next.
    5. On the Choose Issuance Authorization Rules page, select the option Permit all users to access this relying party and click Next.
      note Note:
      You do not need configure individual access for users to single sign-on at this time, because you will manage them from GravityZone Control Center.

    6. On the Ready to Add Trust page:
      1. Go to the Endpoints tab and verify the following addresses have been added:
        • For SAML Assertion Consumer Endpoints: https://gravityzone.bitdefender.com/sp/login, with binding POST.
        • For SAML Logout Endpoints: https://gravityzone.bitdefender.com/sp/logout, with binding Redirect.
      2. Click Next.
    7. On the Finish page, select the option Open the Edit Claim Rules dialog for this relying party trust when the wizard closes.
  6. Click Close.

Creating claim rules

After adding a relying party trust, you need to create claim rules. The Edit Claim Rules window opens once you created the trust.

  1. Click Add Rule to create a new rule.
  2. In Add Transform Claim Rule Wizard, follow these steps:
    1. On the Choose Rule Type page, select the template Send LDAP Attributes as Claims and click Next.
    2. On the Configure Claim Rule page, make the following configuration:
      1. In the Claim rule name box, enter a relevant name (for example, Email).
      2. For Attribute store, select Active Directory.
      3. In the table below, under LDAP Attribute (Select or type to add more), select E-Mail-Addresses.
      4. Under Outgoing Claim Type (Select or type to add more), select E-mail Address.
      5. Click Finish.
  3. Back in the Edit Claim Rules window, click Add Rule to create a new rule.
  4. In Add Transform Claim Rule Wizard, follow these steps:
    1. On the Choose Rule Type page, select the template Transform an Incoming Claim and click Next.
    2. On the Configure Claim Rule page, make the following configuration:
      1. In the Claim rule name box, enter a relevant name (for example, Transform).
      2. For Incoming claim type, select E-Mail Address.
      3. For Outgoing claim type, select Name ID.
      4. For Outgoing name ID format, select Email.
      5. Select Pass through all claim values.
      6. Click Finish.
  5. Click Apply and OK.

Enabling SSO in GravityZone

After configuring AD FS, go to GravityZone Control 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.

  1. Enabling SSO for companies
  2. Changing the authentication method for users

1. Enabling SSO for companies

This is how you enable SSO for your company:

  1. Go to Configuration > Authentication Settings page.
  2. Under Cofigure Single Sign-on using SAML, enter the identity provider metadata URL in the corresponding field. For AD FS, the identity provider metadata URL has the format: https://[:adfshost]/FederationMetadata/2007-06/FederationMetadata.xml, where [:adfshost] is the service FQDN. The other field, reserved for the GravityZone metadata URL, is non-editable.
  3. Click Save.

This is how you enable SSO 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. For AD FS, the identity provider metadata URL has the format: https://[:adfshost]/FederationMetadata/2007-06/FederationMetadata.xml, where [:adfshost] is the service FQDN. The other field, reserved for the GravityZone metadata URL, is non-editable.
  4. Click Save.

2. Changing the authentication method for users

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

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 many GravityZone users as you want, but not for your own administrator account.

note Note:
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.
Can't find a solution for your problem? Open an email ticket and we will answer the question or concern in the shortest time possible.

Rate this article:

Submit