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
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Configuring the SAML integration

Orchestrator user guide
Last updated Feb 13, 2025
- Known limitations
- Prerequisites
- Step 1. Clean up inactive user accounts
- Step 2. Configure the SAML integration
- Step 2.1. Obtain SAML service provider details
- Step 2.2. Configure your identity provider
- Step 2.3. Configure orchestrator
- Step 2.4. Check that the integration is running
- Step 2.5. Configure provisioning rules (optional)
- SAML attribute mapping
- Step 3. Transition your users to SAML SSO
- Step 4. Configure permissions and robots
- Step 5. Discontinue use of local user accounts (optional)
- Considerations for discontinuing use of local accounts