Skip to main content

Thycotic Storage Plugin (Enterprise)

Thycotic Storage Plugin (Enterprise)

Available in PagerDuty Process Automation Commercial products.

Delinea (formerly Thycotic) is a leader in Privileged Access Management solutions providing cloud ready, easy to use security solutions across the complete privileged access surface. A centralized password management system provides visibility and control to protect privileges from attack. Thycotic's solution is built for the Enterprise to enforce strong password business policies and prevent data breaches. Read more about their solution hereopen in new window.

Process Automation users have access to the Thycotic Storage Plugin which can be used to access password/key data stored in a Thycotic Secret Server.


Use the following steps to configure the Thycotic plugin for key storage:

  1. Navigate to the System Menu (gear icon in the upper right).
  2. Click on Key Storage: Key Storage Menu
  3. Navigate to the Configure tab.
  4. Click on Add Storage Plugin +.
  5. Click on Thycotic storage from the popup list.

Fill in the fields for the integration as necessary:

  • Key Storage Path: The path in the Runbook Automation storage tree to apply the plugin. If keys is specified, then all keys and directories added to Key Storage will also be added to Thycotic.
  • Remove Path Prefix: By default, the storage plugin will be invoked using the full path that is requested. If set to true, the path used when invoking the storage plugin would not include the prefix. It is recommended to set this to true. If set to false, keys will not be displayed unless an existing directory is specified in Runbook Automation.
  • Username (Required): Username for an account in Thycotic with access to the secrets that will be used into Runbook Automation.
  • Password (Required): The password for the account in Thycotic with access to the secrets that will be used into Runbook Automation.
  • Address (Required): The base URL for the secret server account where the secrets should be saved. For example, If using Thycotic on-premises, the address must be appended with /SecretServer, so your full URL will be
  • Allow Self Signed Certificate: Set to true if a self-signed certificate will be used to access the Thycotic server.
  • Maximum resources allowed to retrieve This value allows the user to customize the number of resources to retrieve from thycotic.
  • Domain: Fully qualified domain name is using an Active Directory account for integrating with Thycotic.

Below is an example configuration, which can be configured using the System Configuration module. Add each setting as a configuration entry.

Thycotic Configuration

Once the configuration is set, click on Save to add it to the list of configured storage integrations.

Click on Save to commit the configuration.

In the Keys tab, the directory defined in the Path Prefix should now be visible. Click into this directory to begin navigating the secrets from Thycotic.

Thycotic through Enterprise Runner

The Enterprise Runneropen in new window can be used to integrate with Thycotic Secret Server. This is useful when Thycotic is hosted in an environment that is not directly accessible from Runbook Automation.

The following provides examples of how to configure the Enterprise Runner to connect to Secret Server:

YAML Configuration File

Custom properties for the Runner can be set through a .yaml file:

          type: "thycotic-storage"
          pathBehavior: "predefined"
            username: ""
            password: "mythycoticpassword"
            address: ""
            allowSelfSignedCert: "true"
            maximumResources: 30

Save this file in the directory where the Runner .jar is located and then invoke the Runner with the following command:

java -Dmicronaut.config.files=runner-props.yaml -jar runner-{{unique-runner-id}}.jar

Environment Variables

These custom properties can also be set as environment variables on the system where the Runner will be invoked:


When using environment variables, the Runner can be invoked with just:

java -jar runner-{{unique-runner-id}}.jar


Here is an example docker-compose for the Runner with the configuration properties:

version: '3'
      image: ${RUNNER_IMAGE}