- Getting Started
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Specific Scenarios
- Windows Sessions
- Implementing authentication with credential providers
- Redirecting Robots Through a Proxy Server
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike integration
- Robot Citrix Apps Virtualization
- Governance
- Troubleshooting
- Robot Service troubleshooting
- Execution troubleshooting
- Recording and Remote Control troubleshooting
- Networking troubleshooting
- Connection troubleshooting
- Licensing troubleshooting
- Package troubleshooting
- .NET troubleshooting
- Logging troubleshooting
- Session troubleshooting
- CrowdStrike integration troubleshooting

Robot admin guide
Implementing authentication with credential providers
Login using nShield Key Storage Provider
Starting with v2020.10 UiPath integrates nShield Key Storage Provider, making it possible for Unattended Robots to log into Windows by using the nShield Key Storage Provider. nShield is a key storage which provider which allows enterprises, and not only, to provide an extra layer of security when logging into Windows by using the keys stored in the HSM.
Activating this type of login requires a few configuration steps in Orchestrator and on the machine on which the Unattended Robots connect to.
Orchestrator Configuration
- Create an Unattended Robot as described in the Managing Users document with the user specifications for which you want to activate nShield login.
- From the Credential Type drop-down, select nShield Key Storage Provider.
- Provide the PIN required to access the HSM in the Password field.
- Create a Machine in Orchestrator. Please note that the machine on which the Unattended Robot runs needs to have access to the HSM, which means they should be in the same network.
Login using Thales Luna Credential System
As of v2020.4.1, UiPath integrates Thales (previously SafeNet) Luna HSMs, making it possible for Unattended Robots to log into Windows by using the HSM (Hardware Security Module). Thales HSM is a hardware cryptographic key storage that allows enterprises, and not only, to provide an extra layer of security when logging into Windows by using the keys stored in the corresponding HSM.
Activating this type of login requires a few configuration steps in Orchestrator and on the machine on which the Unattended Robots connect to.
Orchestrator Configuration
- Create an Unattended Robot as described in the Managing Users document with the user specifications for which you want to activate Thales login.
- From the Credential Type drop-down, select Luna Credential System.
- Provide the PIN required to access the HSM in the Password field.
- Create a Machine in Orchestrator. Please note that the machine on which the Unattended Robot runs needs to have access to the HSM, which means they should be in the same network.