Use this guide to enable SecureAuth IdP-initiated Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to G Suite (formerly Google Apps).
For Service Provider (SP)-initiated access, refer to G Suite (SP-initiated) Integration Guide
Disclaimer: Enabling Single Sign On (SSO) for G Suite will redirect all users to SecureAuth for authentication. Users who are G Suite Super Administrators can bypass SSO by going directly to https://admin.google.com. Assigning Super Administrators role for select users is recommended in the event of any failures.
1. Have a G Suite account
2. Create a New Realm for the G Suite integration
3. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:
Overview – the description of the realm and SMTP connections must be defined
Data – an enterprise directory must be integrated with SecureAuth IdP
Workflow – the way in which users will access this application must be defined
Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined
1. In the Profile Fields section, map the directory field that contains the user's G Suite ID to the SecureAuth IdP Property
For example, add the G Suite ID Attribute to the Email 2 Property if it is not already contained somewhere else
Tip
Be sure that the G Suite ID includes the domain name, e.g. user@company.com
Warning
Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes
2. Select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin
3. An unalterable URL is auto-populated in the Redirect To field, which appends to the domain name and realm number in the address bar (Authorized/SAML20IdPInit.aspx)
4. Select the SecureAuth IdP Property that corresponds to the directory field that contains the G Suite ID from the User ID Mapping dropdown (Email 2)
5. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)
Select a different option if G Suite requires it, which the SP provides
6. Select False from the Encode to Base64 dropdown
7. Set the WSFed Reply To/SAML Target URL to the G Suite domain email login URL, e.g. https://mail.google.com/a/[company].com
8. Set the SAML Consumer URL to the G Suite domain ACS URL, followed by the Relay State, e.g. https://www.google.com/a/[company].com/acs
9. Set the WSFed/SAML Issuer to the Entity ID value from the Google Admin Console (G Suite Configuration Steps, step 3), e.g. https://accounts.google.com/o/saml2?idpid=12345678
10. Set the SAML Recipient to https://www.google.com/a/[company].com/acs
11. Set the SAML Audience to the SSO URL value from the Google Admin Console (G Suite Configuration Steps, step 3), e.g. https://accounts.google.com/o/saml2/idp?idpid=12345678
12. Set the SAML Offset Minutes to make up for time differences between devices
13. Set the SAML Valid Hours to limit for how long the SAML assertion is valid
Notice
No configuration is required for the SP Start URL field
14. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion
If using a third-party certificate, then click Select Certificate and choose the appropriate certificate
15. Download the Assertion Signing Certificate, which will be sent to G Suite
16. Provide the Domain in order to Download the Metadata File to send to G Suite (if required)
Note
These are optional configurations to enable certain, built-in Google Apps functions
To use these features, G Suite must be configured appropriately
Refer to G Suite Provisioning Configuration Guide for more information
17. Leave the Google Apps Domain Name field blank
18. Set the Admin Email to the G Suite Administrative email account
19. Set the Service Email to the Service Account email address obtained from the G Suite Provisioning Guide (step 18)
20. Click Choose File and select the p12 File obtained in the G Suite Provisioning Guide (step 12)
21. Set the P12 Password to the Private Key Password obtained in the G Suite Provisioning Guide (step 12)
22. Select Enabled from the Create User dropdown if SecureAuth IdP is to automatically create the G Suite user account (if it does not already exist)
23. Select Enabled from the Sync Password dropdown if SecureAuth IdP is to conduct a one-way synchronization of the user's directory password to G Suite
To synchronize on specific dates versus every time the password changes, map a directory field to the Ext. Sync Pwd Date property in the Data tab
If no field is mapped, then the password synchronizes every time
Tip
G Suite requires passwords with a minimum of 8 characters
24. Select Enabled from the Mail Forwarding dropdown if another email address is to receive messages; select Disabled to disable the feature; or select Not Set if SecureAuth IdP is to not be included in this feature
25. Select the Profile Field that contains the user's Forwarding Email Address
Warning
Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes
Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.
1. Log into the G Suite Admin Console
2. Select Security, then click Set up single sign-on (SSO)
3. Note the SSO URL and Entity ID values at the top, as they are required in the SecureAuth IdP Configuration Steps (steps 9 and 11)
4. Check Setup SSO with third party identity provider
5. Set the Sign-in page URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the Google integration realm number, e.g. https://secureauth.company.com/secureauth1/
6. Set the Sign-out page URL to the FQDN of the SecureAuth IdP appliance, followed by the Google integration realm number, and /restart.aspx, e.g. https://secureauth.company.com/secureauth1/restart.aspx
7. Set the Change password URL to the FQDN of the SecureAuth IdP appliance, followed by the Self-service Password Reset realm number (if created), e.g. https://secureauth.company.com/secureauth3/
Follow the Reset Password Configuration Guide to create this realm
8. Upload the Assertion Signing Certificate from the SecureAuth IdP Web Admin (step 15)
9. Click Save Changes