Create a HashiCorp Connector

HashiCorp helps organisations secure, store, and tightly control access to sensitive information such as API keys, passwords, certificates, and encryption keys. The HashiCorp connector serves the purpose of securely accessing cryptographic keys or secrets within HashiCorp Vault.

---

Create a HashiCorp connector

1. Click the 'Configurations' option from the navigation panel.

2. Click the 'Connectors' option.

3. Click theicon from the grid header.

   
4. The 'Add' connector screen will appear to add the connector details. It comprises of two sections, i.e. Basic Information and Details. Specify the basic information and click the button to provide the respective connector details.

5. Click the 'Create' button. A new connector will be saved and displayed in the list. See the table below for field descriptions.

Basic Information
Fields	Description
Name	Specify a unique name for this connector, i.e. HashiCorp Connector. This connector will be used within other connectors, where you want the keys to be fetched from the Key Vault.
Provider	Select the provider for this connector, i.e. "HashiCorp".
Purpose	This field will display the purpose of the selected provider above, i.e. the purpose of "HashiCorp" is "Key Vault".
Active	Tick this check box to make this connector active. Inactive connectors cannot be configured in the other connectors.

The following table describes the fields on the "Details" section of this screen.

Details
Fields	Description
Logo	Select an appropriate image in the jpeg, jpg, gif or png format for the connector's logo that will be displayed, while viewing the selected Key Vault's information within another connector.
UAMI Client ID	Unique identifier for the client application integrating with HashiCorp Key Vault Connector.
Login URL	Specify the URL where the HashiCorp Vault can be accessed for authentication and authorization.
UAMI Name	Specify a unique identifier or label within Azure Active Directory (AD), used to identify and manage individual users or entities within the Azure AD framework, ensuring an organized and secure structure for user-related information and permissions.
Vault Namespace	Specify the logical partition within HashiCorp Vault for organizing and managing secrets. Vault Namespace ensures organized resource management with separate policies, authentication methods, and secrets engines for an efficient and secure environment.
Vault Path	Specify a pathway to a location within the HashiCorp Vault for storing and managing secrets and data.

1. In case a HashiCorp connector has been configured, a new field "Key Vault" will start appearing in the "Details" tab of all other connectors. This field can be used to select an active Key Vault connector for use with connector being currently configured.

2. While the HashiCorp connector is configured within another connector, the HashiCorp connector cannot be deleted or disabled.

3. Once a "Key Vault" has been configured within another connector, a toggle will start appearing against all the text fields of the connector. By default, the toggle for all text fields will be turned off. Turn the toggle on for a field for which you want the value to be fetched from the Key Vault. Once the toggle is turned on, specify the key against which to get the value from the Key Vault.

4. When a Key Vault has been configured within a connector, the toggle should be turned on against at least one of the text fields, and a valid key should be specified with in the field.

5. Except for the below-mentioned connectors, the "Key Vault" drop down will appear in all connectors, if at least one HashiCorp connector has been configured.

   • File Scanning Connector

   • ADFS Connector

   • Freja Mobile Connector