4me cloud application

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

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

Set up SSO via SAML for 4me®

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

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

  1. From the Admin console Home page, go to Appsand thenSAML apps.
  2. Click the plus (+) icon at the bottom right. 
  3. Locate and click 4me in the application list.
  4. On the Google IDP Information page, copy and save the SSO URL.
  5. Click Next.

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

  6. Click Next.

    On the Service Provider Details page, the ACS URL and Entity ID fields are automatically populated.

  7. Replace the occurrences of {your-domain} placeholder in these fields with your 4Me domain. For example, ACS URL (https://{your-domain}.4me.com/access/saml/consume) and Entity ID (https://{your-domain}.4me.com).

    Note: For a 4Me QA account replace TLD from (.com) to .(qa) in both the ACS URL and Entity ID.

  8. The default Name ID is the primary email.
  9. Leave the Name ID Format as Email.
  10. Click Finish.
  11. Click OK.
  12. On the 4me settings page, click Service provider details.
  13. Click Manage certificates.
  14. Copy the SHA-256 fingerprint.
Step 2: Set up 4me as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to the 4me application with your organization's administrator account.
  3. Click Settings and then Single Sign-on.

  4. Check Enable.

  5. In the SAML SSO URL field, enter the SSO URL you copied in step 1.

  6. In the Certificate fingerprint field, paste the certificate fingerprint you copied in step 1.

  7. Click Save changes.
Step 3: Enable the 4me 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 4me.
  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 4me user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working

4me 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 4me.
  4. At the top left, click Test SAML login

    4me 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. Close all browser windows.
  2. Open https://your-domain.4me. You should be redirected to the Google sign-in page.
  3. Enter your user name and password.

After your credentials are authenticated, you are redirected back to 4me.

If the user account authenticated by Google IdP does not already exist in 4Me, you will see an unauthorized error message.

Was this helpful?
How can we improve it?