Configure G Suite as a HyperComply SAML IDP

Have more questions? Submit a request

This guide will take you through the steps for configuring G Suite as the SAML IDP for HyperComply, allowing your users to authenticate to HyperComply through G Suite instead of the usual email/password combination.

  • First we’ll log into HyperComply and copy a value we’ll need for G Suite configuration.
  • Next we’ll create the HyperComply G Suite “Application” and configure it for HyperComply SAML, copying some values back into HyperComply so both parties can trust each other.

HyperComply Configuration

  1. Navigate to
  2. Copy the value of the “SAML ACS Endpoint” at the bottom of the screen.
  3. Keep this tab open and complete the steps below, you will need to enter some values from G Suite on this screen at the end of this process.

G Suite Application Creation

  1. Log in to your G Suite Admin Portal.
  2. Navigate to application settings:
  3. Click ‘Add App’ and then ‘Add custom SAML app’.
    1. Name the new application according to your normal naming convention (‘HyperComply’ works great).
    2. Click “Continue”.
  4. Under “Option 2: Copy the SSO URL, entity ID, and certificate” you’ll find the values needed to enter into the HyperComply SAML Settings (

    Copy the following values into the HyperComply settings:

G Suite Value /

HyperComply Setting


IDP Endpoint URL

Entity ID =

IDP Entity ID

Certificate =

IDP Certificate

Once these values have been copied into HyperComply, make sure the “Enable SAML” checkbox at the top of the page is checked and click “Save”.

Once all values have been copied in the HyperComply settings, click “Continue” in G Suite

  1. On the “Service provider details” page in G Suite:
    1. Copy the “SAML ACS Endpoint” value from HyperComply into the “ACS URL” and “Entity ID” fields in G Suite
    2. Under the “Name ID format” field in G Suite, select “EMAIL”
    3. Leave the “Name ID” field in G Suite as “Basic Information > Primary email”
    4. Click “Continue” in G Suite
  2. Under the “Attributes” section in G Suite
    1. Click “ADD MAPPING”
      1. Under the “Basic Information” field select “First name”
      2. Under the “App attributes field” enter “firstName” 
    2. Click “ADD MAPPING”
      1. Under the “Basic Information” field select “Last name”
      2. Under the “App attributes field” enter “lastName” 
    3. Click “ADD MAPPING”
      1. Under the “Basic Information” field select “Primary email”
      2. Under the “App attributes field” enter “email” 
    4. Click “FINISH”
  3. You will be redirected to the App settings page in G Suite
    1. Make sure you are logged out of HyperComply
    2. Click “TEST SAML LOGIN”
      1. If prompted to allow access:
        1. Click “ALLOW ACCESS”
        2. Select “ON for everyone”
        3. Click the application name in the top menubar to return to the main settings page
        4. Click “TEST SAML LOGIN” again
      2. Known Quirk: If you receive the error “403: not_a_saml_app” from G Suite, you will need to log out of your Google account and log back in to break a cache they hold on their end. Upon logging back in, you should stop receiving this error.


At this point you have connected your G Suite SAML IDP to HyperComply, allowing users to log into HyperComply from G Suite. Any user that logs into HyperComply via G Suite will have an account created for them (if they don’t already have an account). Allowing G Suite users to log into HyperComply can be done by adding and removing Organizational Units to the SAML application through the G Suite admin portal.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful