Skip to main content

G Suite SAML integration

Multi-factor authentication (MFA) is an extra layer of security used when logging into websites or apps to authenticate users through more than one required security and validation procedure that only they know or have access to. Security Assertion Markup Language (SAML) is a protocol for authenticating to web applications. SAML allows federated apps and organizations to communicate and trust one another’s users.

Acceptto™, as a SAML provider, improves the user login experience for G Suite users with convenient MFA, and offers a simple SAML solution for adding MFA and single sign-on (SSO) to G Suite.

Prerequisites

  • An Acceptto account with a configured Identity Provider and LDAP Agent.

    For more information, see the LDAP Agent deployment guide.

  • A G Suite user account with administrative access.

  • A user with administrative privileges for the Acceptto Cloud dashboard.

Acceptto SAML Configuration as Identity Provider (IdP)

  1. Login to the Acceptto Dashboard with an administrative account and go to Applications.

  2. Create a new application by selecting the Create New Application.

    Create new application

  3. In the New Application form, enter the following values under the General tab.

    • Name - The application name displayed in the admin panel and application portal used for push notifications and audit logs. (e.g. G Suite)

    • Type - Select "SAML Service Provider" from the options

    • Out of Band Methods - Select the allowed methods for approving MFA requests

    • Message for MFA Requests - Enter the user-facing message for Push, SMS, and email MFA requests (optional)

    gsuite_add_app.png

  4. Under the SAML Service Provider Configuration tab, enter the following values:

    • Issuer or Entity ID– The Issuer/EntityID of your G Suite instance (e.g. https://www.google.com/a/YOUR-DOMAIN).

    • Sign in URL - The link used by your users to access the G Suite apps (e.g. https://www.google.com/a/YOUR-DOMAIN).

    • Metadata URL - The URL containing metadata about your G Suite instance (e.g. https://www.google.com/a/YOUR-DOMAIN/metadata)

    gsuite_sp_settings.png

  5. Click Save.

Configure ‘G Suite™’ as a Service Provider

  1. Download the SAML metadata and certificate for your organization from Acceptto.

    Metadata Download at https://sso.acceptto.com/<myorganization>/saml/download/metadata or view at https://sso.acceptto.com/<myorganization>/saml/metadata

    Certificate Download at https://sso.acceptto.com/<myorganization>/saml/download/cert

  2. Login to your GSuite admin console.

    gsuite_admin_console.png

  3. Select Security and click on Set up single sign-on (SSO).

    gsuite_security_settings.png

  4. Select Setup SSO with a third party identity provider and fill the fields with the information you got earlier.

    Sign-in page URL - for example, https://sso.acceptto.com/”your organization”/saml/auth

    Sign-out page URL - for example, https://sso.acceptto.com/”your organization”/saml/logout

    Verification certificate - click add file, and select the certificate file received earlier from the https://sso.acceptto.com/”your organization”/saml/download/cert

    gsuite_sso_config.png

  5. Select Save.

Test your application integration

  1. Go to your Google App link. You will be redirected to the Acceptto SAML page.

    acceptto login

  2. After successful authentication, the Acceptto MFA options will appear. Select your desired method. Then, pass the authentication request on the It’sMe mobile app.

    Select MFA method

  3. Finally, you will be redirected to your Google app landing page.

Support

If you have questions or need assistance, contact SecureAuth Support.

Sales

Want to learn more about our MFA solutions? Contact our Professional Services for a demo today.

Disclaimer

All product names, trademarks, and registered trademarks are the property of their respective owners.

All company, product, and service names used in this document are for identification purposes only. The use of these names, trademarks, and brands do not constitute an endorsement by the SecureAuth Corporation.

In this section: