- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
- Host Administration Portals
- Configuring System Email Notifications
- Managing System Administrators
- Configuring Host Security
- Host Audit Logs
- Customizing the Login Page
- Maintenance Mode
- Managing tags
- Audit Logs
- Overriding System Email Settings
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:
- The following details must be provided on the Service Provider window:
https://orchestratorURL/identity/Saml2/Acsas the ACS URL
https://orchestratorURL/identityas the Entity ID
- 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.Note: If you are still using the old Admin experience, go to Users instead of 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.