Credential management

4 minute readSecurity

Credentials are used to access services and resources used during application deployments, release pipeline execution, or any other automated process orchestrated by CloudBees CD/RO. Credentials are supported in the following contexts.

  • Stored credentials used by a process step, plugin tasks or procedure step

  • Stored credentials used for impersonation

  • Credential parameters

  • Username and password or secret supplied at runtime

Two credential types are available, stored and runtime:

  • Stored credentials: Each project has a list of stored credentials it owns. You manage these credentials on the Credential Management page.

    • Internally-managed credentials: These credentials are stored in encrypted form in the CloudBees CD/RO database.

    • Externally-managed credentials: These credentials are stored and managed via an external credential provider. Supported external providers include CyberArk and HashiCorp Vault.

  • Runtime credentials: These credentials are dynamically captured when a job run-time object is created. Dynamic credentials are stored on the server temporarily until the job completes and then discarded.

Stored credential encryption

Internally managed credential data, including passwords, uses 256-bit AES (Advanced Encryption Standard).

Creating a credential provider definition

Creating a credential provider definition is a one-time process per provider instance at your site. The following external credential providers and options are supported:

  • CyberArk:

    • Central Credential Provider (CCP)

    • CyberArk Dynamic Access Provider (DAP)

  • HashiCorp Vault:

    • Vault Cubbyhole

    • Vault Key/Value (KV) 1

    • Vault Key/Value (KV) 2

For external credential provider version information, refer to Supported external credential providers.

If you are using one of these external credential providers to manage credentials, the following sections explain the steps to create and define its provider definition within CloudBees CD/RO.

If you are creating an internally-managed credential, refer to defining a credential.


  • A supported external credential provider is installed and configured for your site.

  • You have credentials configured with your credential provider.

  • You are able to provide the external credential provider instance details required to define the provider definition within CloudBees CD/RO.

  • You have a CloudBees CD/RO project to store the credential provider definition and credentials it manages.

    CloudBees suggests organizing your credentials based on use across your environment. For example, you may have one project for staging providers and another project for production providers, each with their own credential provider. In other cases, it may be appropriate to base project organization on user groups with specific credentials.

Define the provider

  1. From the CloudBees CD/RO main menu, navigate to DevOps Essentials  Credential Management and select Credential providers.

  2. Select Add credential provider to open the New Credential Provider dialog.

  3. On the Details tab, provide the CloudBees CD/RO details for your credential. Pay close attention to the following fields:

    • Name: This is the name you reference when defining externally-managed credentials within CloudBees CD/RO as described in Defining a credential.

    • Project: The CloudBees CD/RO project where to store the definition.

      Once a project is selected and the credential created for it, the project cannot be altered. If the project must be changed, you must delete the existing credential definition and create a new one.
  4. To provide the credential definition, select the Definition tab.

  5. To specify a credential provider, select the Provider type dropdown, and choose the credential provider for your project.

  6. After choosing the credential provider, select the supported credential option.

  7. Provide all information required for the credential definition, and select OK.

This provider definition is now available when creating an external credential.

Defining a credential

After a credential is created, no one can access the password for the credential’s account. This means one person can define a credential and enter the password, and other people can use the credential (and its account) without needing to know the password.

  1. From the CloudBees navigation, select CloudBees CD/RO.

  2. From the CloudBees CD/RO main menu, navigate to DevOps Essentials  Credential Management and select Credentials.

  3. Select Add credential to open the New Credential dialog.

  4. Enter the following:

    • Name: User-defined name of this provider definition. You use this name within CloudBees CD/RO at credential definition time.

    • Project: The CloudBees CD/RO project under which this definition is created.

    • Description: (optional) Comment text describing this definition. This is not used internally by CloudBees CD/RO.

    • User name: The name under which you want to log in for this credential definition.

  5. Select Credential provider type and enter:

    • For internally-managed credentials, enter the password for this credential.

    • For externally-managed credentials, enter the following:

      For external credentials, you are registering a credential you have previously defined with your credential provider.
      • Credential provider project: The project under which the provider definition resides.

      • Credential provider: The name of the previously created provider definition.

      • Secret path: The path to the folder where the password is stored.

Alternate process

Credential and credential provider management is also available from the automation platform UI and the CloudBees CD/RO project list.

  • Automation platform:

    1. Select the Projects tab.

    2. Select a project (first column) to access the Project Details page.

    3. Select the Credential Provider tab, and then select Create Credential Provider

    4. Select the Credential tab, and then select Create Credential

      • Provide details as described in Defining a credential.

        Select Help on the New Credential page if you need more details about what to enter.

  • Projects list (support for creating credentials, only):

    1. Navigate to DevOps Essentials  Projects list.

    2. From the Projects list, select Actions Actions selector for the desired project, and then select Details. The Project edit dialog displays.

    3. Select the Manage Credentials right arrow button to open the Credentials dialog.

    4. Select Add to open the Credential dialog. Enter data into the fields as described in Defining a credential.

    5. Select OK to save the credential.