iMeet Central 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 iMeet Central

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

Step 1: Set up Google as a SAML identity provider (IdP)
  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 Add Add at the bottom right.
  4. Locate and click iMeet Central in the application list.
  5. On the Google IDP Information page:
    • Copy and save the SSO URL.
    • Download the Certificate.
  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,  replacing {your‑domain} with your iMeet Central 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
    username Basic Information Primary Email
    firstname Basic Information First Name
    lastname Basic Information Last Name
    email Basic Information Primary Email
  11. Click Finish.
Step 2: Set up iMeet Central as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to iMeet Central with your administrator account.
  3. Navigate to Company Setup > Advanced > Single Sign-On.
  4. (Optional) Check Automatically create new users to create new users via just-in-time provisioning, and choose their role.
  5. Choose Issuer Public Cert from the dropdown menu, then paste the contents of the certificate you downloaded in Step 1 into the field.
  6. In the Issuer URL field, paste the SSO URL you copied in Step 1 above.
  7. Choose First/Last Name Attribute from the dropdown menu, then enter ‘firstname’ in the upper field and ‘lastname’ in the lower field.
  8. Choose Email and Username from the dropdown menu, and enter email and username information in the respective fields. (If the Username field is not available, select email instead.)
  9. Check Enable SAMLv2 Single Sign On.
Step 3: Enable the iMeet Central 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 iMeet Central.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To apply settings to all organizations, click On for everyone or Off for everyone, and then click Save

  6. To apply settings to individual organizational units, do the following: 

    • At the left, select the organizational unit that contains the users whose settings you want to change.
    • To change the setting, select On or Off.
    • To keep the setting the same, even if the parent setting changes, click Override.
    • 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 the organizational structure.

  7. Ensure that your iMeet Central user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working
  1. Close all browser windows.
  2. Open https://{your_domain}.imeetcentral.com/saml2-assertion.php, replacing {your_domain} with your iMeet Central subdomain, and attempt to sign in. You should be automatically redirected to the Google sign-in page.
  3. Enter your username and password.

After your sign in credentials are authenticated, you are automatically redirected back to iMeet Central.

Was this article helpful?
How can we improve it?