- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Configuring SSO: Google
By configuring and enabling Google as an external identity provider in Orchestrator, you add an option for Google authentication to the Login page.
Prior to enabling Google SSO, you must create authorization credentials for Orchestrator from the Google Console.
Now you must configure Google as an external identity provider in Orchestrator.
Now that Orchestrator is integrated with Google Sign-In, user accounts that have a valid Google email address can use the Google SSO option on the Login page to sign in to Orchestrator.
Each organization administrator must do this for their organization/tenant if they want to allow login with Google SSO.
- Log in to Orchestrator as an administrator.
- Add local user accounts, each with a valid Google email address.