orchestrator

2022.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
- Organizing Resources With Tags
- Orchestrator Read-only Replica
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Managing Access and Automation Capabilities
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
- Settings
Resource Catalog Service
- About Resource Catalog Service
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
- Running Personal Remote Automations
- Troubleshooting Jobs
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
- Storing Assets in Azure Key Vault (read-only)
- Storing Assets in HashiCorp Vault (read-only)
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
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Managing your host license
  - Allocating Licenses to Tenants
    - Allocating Host Licenses to Tenants
- Configuring system email notifications
- Configuring other host settings
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- Managing organization administrators
- Managing organization settings
- Configuring organization authentication
- Configuring Security Options
  - Session policy
- About Licensing
  - Activating your license
- Accounts and Groups
  - Managing access
  - Managing accounts and groups
- Authorizing external applications
  - Managing external OAuth applications
- Overriding System Email Settings
- Audit logs
Troubleshooting
- About Troubleshooting

Orchestrator User Guide

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Oct 9, 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 Security.
Click 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.
Click Save to save the changes to the external identity provider settings.

The page closes and you return to the Security Settings page.
Click the toggle to the left of Google SSO to enable the integration.
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-2024 UiPath. All rights reserved.