Prerequisites
Before you begin, you’ll need:- Super administrator access to your Google Workspace Admin Console
- The SSO configuration details from Ally Security (we’ll provide these after you request SSO setup)
- The email domain(s) that should be enabled for SSO
Step 1: Create a New SAML App in Google Workspace
- Navigate to the Google Admin Console and sign in with your administrator account.
- In the Admin Console, navigate to Apps > Web and mobile apps.
- Click Add app and select Add custom SAML app.
Step 2: Enter App Details
- Enter an App name (e.g., “Ally Security”).
- Optionally, upload an app icon and enter a description.
- Click Continue.
Step 3: Download IdP Metadata
On the Google Identity Provider details page:- Click Download Metadata to download the IdP metadata XML file. You will need to share this file with Ally Security.
- Alternatively, you can copy the SSO URL, Entity ID, and Certificate individually if Ally Security requests these values separately.
- Click Continue.
Step 4: Configure Service Provider Details
You’ll need to enter the following information that we (Ally Security) will provide to you:- ACS URL: Paste the ACS URL (Assertion Consumer Service URL) provided by Ally Security.
- Entity ID: Paste the Entity ID provided by Ally Security.
- Start URL: Leave this field empty unless Ally Security provides a specific value.
- Signed response: Check this box if requested by Ally Security.
- Name ID format: Select EMAIL from the dropdown.
- Name ID: Select Basic Information > Primary email from the dropdown.
- Click Continue.
Step 5: Configure Attribute Mappings
Ally Security requires specific attributes in the SAML response. Configure the following attribute mappings:-
Click Add mapping and add the following attributes:
Email address (required)
- Google Directory attribute: Select
Primary email - App attribute: Enter
mail
- Google Directory attribute: Select
First name - App attribute: Enter
firstName
- Google Directory attribute: Select
Last name - App attribute: Enter
lastName
- Google Directory attribute: Select
- Click Finish to complete the app creation.
Step 6: Enable the App for Users
After creating the app, you need to enable it for your users:- On the app details page, find the User access section.
- Click User access to expand the settings.
- To enable for all users:
- Select ON for everyone.
- To enable for specific organizational units:
- Click on the specific organizational unit in the left panel.
- Select ON for that organizational unit.
- Click Save.
Changes may take up to 24 hours to propagate to all users, though they typically take effect within a few minutes.
Step 7: Share the IdP Metadata with Ally Security
After completing the setup in Google Workspace, provide Ally Security with your app’s metadata:- Return to the app details page in Google Admin Console.
- Click Download metadata to download the metadata XML file.
- Send this metadata file to your Ally Security contact or support team.
- SSO URL: The URL users will be redirected to for authentication
- Entity ID: The unique identifier for your Google Workspace as the identity provider
- Certificate: The X.509 certificate for verifying SAML assertions
What to Provide to Ally Security
To complete the SSO setup, please provide the following information:- IdP Metadata file: The metadata XML downloaded from Google Admin Console (as described in Step 7)
- Email domain: The email domain(s) that should be enabled for SSO (e.g.,
@yourcompany.com) - Test user email (optional): An email address of a test user that can be used to verify the SSO configuration
After Setup Is Complete
Once Ally Security has configured SSO on our end:- All users with email addresses ending in your configured domain will be redirected to Google for authentication
- Users will sign in using their Google Workspace credentials
- Existing users with matching email domains will need to use SSO to sign in
Troubleshooting
If you encounter issues during setup:- Verify attribute mappings: Ensure that the attribute names (
mail,firstName,lastName) match exactly as specified - Check user access settings: Confirm that the app is enabled for the users who need to sign in
- Verify domain configuration: Ensure the email domain matches what was provided to Ally Security
- Check the metadata file: Ensure you’ve provided the complete, unmodified metadata XML file
- Review Google Admin logs: Check the Admin Console audit logs for any SAML-related errors
- Contact support: Reach out to Ally Security support if you need assistance with the configuration
