- Microsoft SSO
- Google SSO
- Login via E-Mail
- Google SSO
- Microsoft SSO
- Login via E-Mail
This guide will walk you through setting up Single Sign-On (SSO) with Google Workspace for Genow. This integration allows your users to sign in using their Google Workspace credentials.
Prerequisites
- A Google Workspace account
- A Google Cloud Project
- Administrator access to your Genow instance
Step 1: Project Setup
- If Genow runs in a different tenant than your Google Workspace:
- Go to the Google Cloud Console
- Create a new project for oAuth Settings
- If Genow runs in the same tenant as your Google Workspace:
- Use the existing Genow platform project
Step 2: Configure OAuth Client
- In Google Cloud Console, navigate to APIs & Services > Credentials
- Click Create Credentials > OAuth client ID
- Configure the OAuth consent screen:
- User Type: Internal
- App name: “Genow SSO”
- User support email: Your admin email
- Developer contact information: Your contact email
- Create OAuth 2.0 Client ID:
- Application type: Web application
- Name: “Genow SSO”
- Authorized JavaScript origins: Add your Genow platform’s identity platform origins
- Authorized redirect URIs: Add your Genow platform’s identity platform redirect URIs
Note: The exact origins and redirect URIs will be provided by your Genow platform administrator
- Click Create
- Save the generated:
- Client ID
- Client Secret
Step 3: Configure Genow
- Log in to your Genow instance as an administrator
-
Add the following information to the Genow Platform’s Secret Manager:
FIREBASE_CLIENT_ID: Your Google Client IDFIREBASE_CLIENT_SECRET: Your Google Client Secret
-
After adding the secrets, run the following commands to update the infrastructure:
- Wait for the infrastructure updates to complete
Step 4: Test the Integration
- Sign out of Genow
- Click the “Sign in with Google” button
- You should be redirected to Google’s login page
- After successful authentication, you should be redirected back to Genow
Important Notes
- The authentication is handled through Google’s OAuth 2.0 protocol
- We recommend providing access to your Google Cloud project to our support team for better assistance
- Additional documentation for application roles and user permissions will be provided separately
Troubleshooting
If you encounter any issues:- Verify all configuration values are correct
- Ensure the authorized origins and redirect URIs match exactly
- Check that users exist in both systems
- Review the Genow logs for any error messages
- Verify that the OAuth consent screen is properly configured
- Confirm that the project has the necessary APIs enabled
Security Considerations
- Regularly rotate the client secret
- Monitor sign-in logs for suspicious activity
- Keep your Google Cloud project secure
- Review and audit user access regularly
- Consider implementing additional security measures like 2FA
