Federated Directory cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Federated Directory

Here's how to set up single sign-on (SSO) via SAML for the Federated Directory® application.

Step 1: Get Google identity provider (IdP) information
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the plus (+) icon at bottom right.
  4. Locate and click Federated Directory in the application list.
  5. On the Google IDP Information page:
    • Copy and save the SSO URL.
    • Download the Certificate.

Leave the Admin console open, you'll continue with the SSO configuration wizard after performing the next step in the Federated Directory application.

Step 2: Set up Federated Directory as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to http://www.federated.directory with your organization's Federated Directory account.
  3. Click the menu icon at top left, then Directories.
  4. Select the directory you want to connect to G Suite, then the Config tab.
  5. Copy the id and save it (you'll need this value when you return to the Admin console to finish configuring SSO for Federated Directory).
  6. Under Authentication method, select SAML authentication.
  7. In the Login page URL field, enter the SSO URL you copied in Step 1.
  8. In the Verification certificate field, paste the contents of the certificate file you downloaded in Step 1.
  9. Click Save authentication method to save your changes, then close your incognito browser window and return to the Admin console to continue configuration.
Step 3: Finish SSO configuration in Admin console
  1. In the SSO configuration wizard, click Next.

    The Basic information window shows the Application name and Description seen by users.

  2. Click Next.
  3. On the Service Provider Details page, edit the default contents of the ACS URL and Entity ID fields, replacing {directoryId} with the Directory ID you copied from the Federated Directory SSO settings in Step 2 above.
  4. Click Finish.
Step 4: Enable the Federated Directory app
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Select Federated Directory.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. To turn on or off a service only for users in an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. To keep the service turned on or off even when the service is turned on or off for the parent organizational unit, click Override.
    4. If the organization's status is already Overridden, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. Ensure that your Federated Directory user account email IDs match those in your Google domain.
Step 5: Verify that the SSO is working
  1. Close all browser windows.
  2. Open https://www.federated.directory/of/{your_company_name}
    and attempt to sign in. You should be automatically redirected to the Google sign in page.
  3. Enter your sign in credentials.
  4. After your sign in credentials are authenticated, you are automatically redirected back to Federated Directory.
Step 6: Set up user provisioning

As a super administrator, you can automatically provision users in the Federated Directory application.

Was this helpful?
How can we improve it?