orchestrator

2021.10

false

Getting started
- Introduction
- User Options
- Logging in to Orchestrator
- Resetting Your Password
- My Profile
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
Tenant
- About the Tenant Context
- Robots
- Folders
- Managing Access and Automation Capabilities
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
  - Setting Up Alert Emails
- Settings
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- About Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
Triggers
- About Triggers
- Managing Triggers
- Using Cron Expressions
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
Test Suite - Orchestrator
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
Integrations
- About Input and Output Arguments
  - Providing Argument Values
    - Orchestrator API
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Best Practices
  - Managing Environments
- Jobs
  - Long-Running Workflows
    - Queues
    - Duration
- Triggers
  - Time Triggers
    - Queued Jobs Scenarios
  - Queue Triggers
- Monitoring
  - Robots
- Resources
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Managing your host license
  - Allocating host licenses to organizations
- Configuring system email notifications
- Configuring other host settings
  - Customizing the Login page
  - Orchestrator host settings
    - Tenant Settings - Host Level
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- About Licensing
  - Activating your license
- Accounts and Groups
- Registering External Applications
  - Managing External Applications
- Audit logs
Troubleshooting
- About Troubleshooting
- Cron Expressions
- Upgrade Issues
- Frequently Encountered Orchestrator Errors

OUT OF SUPPORT

Orchestrator User Guide

DELIVERY:

Last updated Oct 31, 2024

Google Authentication

Configure Google to Recognize a New Orchestrator Instance

Note: The below steps are valid for Google SSO setup. Please note that the below 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 URL
- https://orchestratorURL/identity as the Entity ID

Set Orchestrator/Identity Server to Use Google Authentication

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 Users and select the Security Settings tab.
In the External Providers section, click Configure under SAML 2.0:

The Configure SAML 2.0 panel opens at the right of the window.
Set it up as follows:
- Select the Enabled check box.
- Set the Service Provider Entity ID parameter to https://orchestratorURL/identity.
- Set the Identity Provider Entity ID parameter to the value obtained by configuring Google authentication.
- Set the Single Sign-On Service URL parameter to the value obtained by configuring Google authentication.
- Select the Allow unsolicited authentication response checkbox.
- Set the Return URL parameter to https://orchestratorURL/identity/externalidentity/saml2redirectcallback.
- Set the External user mapping strategy parameter to By user email.
- Set the SAML binding type parameter to HTTP redirect.
- In the Signing Certificate section, set Store name parameter to My from the drop-box.
- Set the Store locationparameter to LocalMachine.
- Set the Thumbprint parameter to the thumbprint value provided in the Windows certificate store. Details here .
  
  Note:
  Replace all occurrences of https://orchestratorURL with the URL of your Orchestrator instance.
  
  Make sure that the URL of the Orchestrator instance does not contain a trailing slash. Always fill it in as https://orchestratorURL/identity, not https://ochestratorURL/identity/.
Click Save to save the changes to the external identity provider settings.
Restart the IIS server.

On this page

Configure Google to Recognize a New Orchestrator Instance
Set Orchestrator/Identity Server to Use Google Authentication

Was this page helpful?

PREVIOUSADFS Authentication

NEXTOkta Authentication

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2025 UiPath. All rights reserved.