Orchestrator

latest

false

- Introduction
- - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Activities Feeds
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Organization Modeling in Orchestrator
- 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
- Audit
- - Types of Events
  - Managing Webhooks
- - Managing Your Licenses
- Settings
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- About the Folders Context
- Home
- About Automations
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- - Troubleshooting live streaming and remote control
- About Jobs
- Managing Jobs
- Job States
- Working With Long-running Workflows
- Running Personal Remote Automations
- Process Data Retention Policy
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
- Managing Non-Working Days
- - Triggering jobs on the last day of the month
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
- 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)
- Storing Assets in AWS Secrets Manager (read Only)
- - CORS/CSP Configuration
- Managing Storage Buckets
- Test Automation
- - Field Descriptions for the Test Cases Page
- - Field Descriptions for the Test Sets Page
- - Field Descriptions for the Test Executions Page
- - Field Descriptions for the Test Schedules Page
- About Resource Catalog Service
- About Authentication
- SmartCard Authentication
- Configuring the SMTP Server
- - Example of Using Input and Output Arguments
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Storing Unattended Robot Credentials in HashiCorp Vault (read-only) - Automation Cloud latest

Orchestrator User Guide

Last updated Nov 28, 2023

Storing Unattended Robot Credentials in HashiCorp Vault (read-only)

Note: Before performing the following procedure, make sure you have configured your HashiCorp Vault (read-only) integration.

When storing an unattended robot password in a read-only credential store, you must create the secret in Vault and make sure you meet the following requirements:

the path of the secret must contain the data path configured for the credential store, concatenated with the External Name configured for that robot. For example. if the data path is applications/orchestrator/robots, and the External Name is robot01, then the secret's path must be applications/orchestrator/robots/robot01.
inside the secret, you must have a key named Value, and the value must be this robot's password.

PREVIOUSStoring Unattended Robot Passwords in Azure Key Vault (read-only)

NEXTStoring Unattended Robot Credentials in AWS Secrets Manager (read Only)

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2023 UiPath. All rights reserved.