orchestrator
2023.10
false
- 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
- Orchestrator testing
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting

Orchestrator user guide
Last updated Sep 3, 2025
Google Authentication
linkConfigure Google to Recognize a New Orchestrator Instance
linkNote: The following steps are valid for Google SSO setup. Note that the following procedure is a broad description of a sample configuration. For a fully detailed how-to, visit the official Google documentation.
If you do not have the necessary permissions, address to your system administrator in this regard. Make sure that the following service details are set into place:
- The service must be set as ON for everyone.
- The following mappings must be provided for Orchestrator attributes on the Attribute Mapping window:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
-
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn
- The following details must be provided on the Service Provider window:
https://orchestratorURL/identity/Saml2/Acs
as the ACS URLhttps://orchestratorURL/identity
as the Entity ID
Set Orchestrator/Identity Server to Use Google Authentication
link- Define a user in Orchestrator and have a valid email address set on the Users page.
- Import the signing certificate provided by the Identity Provider to the Windows certificate store using Microsoft Management Console.
- Log in to the Management portal as a system administrator.
- Go to Security.
- Select Configure under Google SSO:
The Google SSO configuration page opens.
- Set it up as follows:
- Optionally select the Force automatic login using this provider checkbox if, after the integration is enabled, you want your users to only sign in using Google authentication.
- In the Display Name field, type the name that you want to show for the SAML login option on the Login page.
- In the Client ID field, add the value obtained while configuring Google.
- In the Client Secret field, add the value obtained while configuring Google.
- Select Save to save the changes to the external identity provider settings.
The page closes and you return to the Security Settings page.
- Select the toggle to the left of Google SSO to enable the integration.
- Restart the IIS server.