Delinea Secret Server
Connector maturity: Beta. See Connector maturity.
Description
The Delinea Secret Server connector (formerly Thycotic Secret Server) uses the Secret Server REST API to discover managed secrets and their folder structure. It authenticates using the OAuth 2.0 password-grant flow and enumerates all secrets visible to the scanning user, recording secret folder paths as entitlements.
System Type Classification
| Field | Value |
|---|---|
| System Type | PAM Tool |
| Default Scan Priority | 500 |
Set System Type = PAM Platform to feed scan results into PAM Inventory/Reconciliation (the default for new Delinea Secret Server systems). Set System Type = Application instead to list the same accounts on the Accounts/Entitlements pages, like any other target system.
Version Support
| OrbisID Edition | Supported |
|---|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|---|---|
| REST API (HTTPS) | 443 TCP | OAuth 2.0 password grant |
What OrbisID Discovers
| Data | Source |
|---|---|
| Managed secrets (accounts) | GET /api/v1/secrets (paginated) |
| Secret username | Secret username field or Username item |
| Secret folder path | folderPath field — recorded as DELINEA_FOLDER entitlement |
| Secret template name | secretTemplateName — stored as metadata |
Connection Requirements
Secret Server User Account
OrbisID authenticates as a local Secret Server user with view access to target secrets.
Minimum permissions:
- View Secret on all secrets or folders to be scanned
- View Folder on the target folder hierarchy
Recommended: Create a dedicated user (e.g., orbisid-scanner) and assign view-only permissions on the folders to be scanned.
Credential Mapping
| OrbisID Field | Secret Server Value |
|---|---|
credential.username | Secret Server local username |
credential.password | Secret Server password |
system.pamPlatformUrl | Base URL (e.g., https://secretserver.example.com) |
Network Requirements
The OrbisID server (or On-Premise Agent) must have HTTPS access to the Secret Server on port 443.
Configuration Steps
- Create a dedicated Secret Server user with view access to target folders
- Create a Credential in OrbisID:
- Username: Secret Server username
- Password: Secret Server password
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|---|
| Name | Descriptive name (e.g., Delinea Secret Server – Production) |
| PAM Platform URL | Base URL of Secret Server (e.g., https://secretserver.example.com) |
| OS Type | Delinea |
| System Type | PAM Tool |
| Credential | The scanning user credential |
- Click Test Connection to verify authentication
- Click Save
For Delinea Cloud (Secret Server Cloud), use your tenant URL: https://<tenant>.secretservercloud.com. The same REST API and credential format apply.
Onboarding accounts into Secret Server
Requires Enterprise edition.
OrbisID can also add privileged accounts that are not in Secret Server to it. See Vault Onboarding for how batches, approval and rollback work. In the onboarding rules, the Folder is a Secret Server folder path (for example Servers\Windows) and the Secret template is a template name or numeric ID. This is what Secret Server needs:
- A write credential. Create a separate user for this. It needs permission to create secrets in the target folders, to view and change passwords on them (so it can change and check the password), and to delete secrets (for rollback). It also needs to see the folders and templates. For scanning, a read-only credential is enough; this is not.
- Existing folders. OrbisID never creates a folder. The folder named by your rule must exist, and must be identified by its full path (or by a name that only one folder has).
- A template OrbisID can fill. The template must have a password field, and its only required fields must be the user name, the machine (or host or server) and, optionally, notes. A template that requires anything else, such as a domain, is shown as Blocked.
- A way to reset the password. Secret Server must be able to change the account's password without knowing the current one, through a privileged (reset) account set up on the template or secret. OrbisID cannot read that setting, so on the Secret Server system tick Secret Server can reset these accounts' passwords once you have set it up. Until you do, every account is shown as Blocked and nothing is written. Remote password changing and heartbeat must also be enabled on the template.
- A site. New secrets are created in site 1 unless you set Site ID for new secrets on the system.
Secret Server needs a password on every secret, and OrbisID does not have the account's password. So each secret is created with a one-off random password that OrbisID never stores or shows, with automatic password changing turned on. OrbisID then asks Secret Server to change the account's password and to check it (a heartbeat). Only if the check succeeds is the account counted as onboarded: that proves Secret Server now holds a password that works on the real account. If the change or the check fails, the secret is deleted again, so no secret holding an invented password is left behind.
Secrets are named account@machine. Rolling back deletes the secrets the batch created; Secret Server may keep a deleted secret as inactive.
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
Authentication failed on test connection | Invalid credentials | Verify username and password; ensure the account is active and not locked |
| No secrets returned | User has no view access to secrets | Grant View Secret on target folders for the scanning user |
| PAM Platform URL not found | URL incorrect or Secret Server unreachable | Verify the URL; check network connectivity on port 443 |
401 on secret detail fetch | Token expired during long scan | Reduce the number of secrets in scope or increase connection timeout |