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 thenWeb and mobile apps.
  3. Click Add appand thenSearch for apps.
  4. Enter LiquidFiles in the search field.
  5. In the search results, hover over the LiquidFiles SAML app and click Select.
  6. On the Google Identity Provider details page, copy and save the SSO URL and the SHA-256 fingerprint.
  7. Click Continue.
  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 Continue.
  10. On the Attribute Mapping page, click the Select field menu and map the following Google directory attributes to their corresponding LiquidFiles attributes:
     
    Google directory attribute LiquidFiles attribute
    Basic Information > First Name User.FirstName
    Basic Information > Last Name User.LastName
  11. Click Finish.
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 an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile 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. (Optional) To turn a service on or off for an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. Click Override to keep your setting if the service for the parent organizational unit is changed.
    4. If Overridden is already set for the organizational unit, 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 an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile 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.



Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue