LiquidFiles 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 LiquidFiles

Here's how to set up Single Sign-On (SSO) via SAML for the LiquidFiles® application.

Step 1: Set up Google as a SAML identity provider (IdP)
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenSAML apps.
  3. Click Add at the bottom right.
  4. Locate and click LiquidFiles in the application list.
  5. On the Google IDP Information page, copy and save the SSO URL.
  6. Click Next.

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

  7. Click Next.
  8. On the Service Provider Details page, edit the ACS URL, Entity ID, and Start URL, replacing {your‑hostname} with your LiquidFiles subdomain.
  9. Click Next.
  10. On the Attribute Mapping page, set the Select category and Select user field values as follows for the listed attributes:
     
    Application attribute Select category Select user field
    User.FirstName Basic Information First Name
    User.LastName Basic Information Last Name
  11. Click Finish.
  12. Click OK.
  13. On the LiquidFiles settings page, click Service provider details.
  14. Click Manage certificates.
  15. Copy the SHA-256 fingerprint.
Step 2: Set up LiquidFiles as a SAML 2.0 service provider (SP)
  1. Sign in to LiquidFiles with your administrator account.
  2. Navigate to Admin > Configuration > Single Sign-On.
  3. For Single Sign On Method, choose SAML 2.
  4. Enter information in the following fields:
    • IdP Login URL: the SSO URL you copied in Step 1.
    • IdP Cert Fingerprint: the SHA-256 fingerprint you copied in Step 1.
  5. For Signature Algorithm, choose SHA-256.
  6. Click Save.
Step 3: Enable the LiquidFiles 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 Appsand thenSAML apps.
  3. Select LiquidFiles.
  4. Click User access.
  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. (Optional) Turn on the service for a group of users.
    Use access groups to turn on a service for specific users within or across your organizational units. Learn more

  8. Ensure that your LiquidFiles user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working

LiquidFiles supports both Identity Provider (IdP) initiated and Service Provider (SP) initiated SSO. Follow these steps to verify SSO in either mode:

IdP-initiated

  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 Appsand thenSAML apps.
  3. Select LiquidFiles.
  4. At the top left, click Test SAML login

    LiquidFiles should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.

SP-initiated

  1. In a new browser window,  go to https://{your-hostname}.liquidfiles.com/saml/init. You should be automatically redirected to the Google sign-in page.
  2. Enter your username and password.

After your sign in credentials are authenticated, you're automatically redirected back to LiquidFiles.

Was this helpful?
How can we improve it?