Almacenes de credenciales

Nota:

La disponibilidad de las características depende de la oferta en la nube que utilices. Para obtener más información, consulta la página Disponibilidad de características.

A credential store is a named location within a secure store, such as CyberArk®, from which you can store and retrieve sensitive data such as Robot credentials and credential assets when needed. Orchestrator supports the use of multiple credential stores at tenant level, and provides built-in support for Azure Key Vault, CyberArk Secrets Manager, HashiCorp Vault, Thycotic Secret Server, BeyondTrust, AWS Secrets Manager, and Google Secret Manager. It also provides the necessary architecture to add and manage third party secure stores, if desired.

For Automation Cloud, Test Cloud, and Automation Cloud Dedicated, the Credentials page is split in two views: Stores and Proxies.

• The Stores page allows you to create new stores, view existing stores and their properties, and delete any current credential store. Note that the native Orchestrator Database store is automatically created, will always appear first in this list and be the Default store for all new tenants.
• The Proxies page allows you to create new proxies for your own custom credential stores, view a list of existing proxies, edit, and remove them.

For Automation Cloud Public Sector and Test Cloud Public Sector, the Stores page allows you to create new stores, view existing stores and their properties, and delete any current credential store. Note that the native Orchestrator Database store is automatically created, will always appear first in this list and be the Default store for all new tenants.

Nota:

El administrador de Orchestrator debe habilitar la función de almacenamiento de credenciales para tu tenant. Obtén más información aquí.

Nota:

Managing credential stores in Orchestrator requires specific privileges because credential stores contain sensitive authentication data used by automations. To create, modify, or delete credential stores, a user must have Settings permissions (View, Edit, Create, and Delete). These permissions are included in the Orchestrator Administrator role. If the Settings permissions are removed from a role, the user will no longer be able to manage credential stores.