# Store Account

{% hint style="info" %}
This is a Pipeline Engine v2 exclusive connector.
{% endhint %}

**Store Account** dynamically stores accounts locally and later in a vault, playing a crucial role in security.

To enable the dynamic use of accounts in different connectors, you need to follow a two-step process:

1. Store the desired account using the **Store Account** connector.
2. Reference the name of the account in the connector in which you want to use it.

{% hint style="info" %}
The connector must support the [Dynamic Accounts feature](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/overview/runtime/pipeline-engine/dynamic-accounts).
{% endhint %}

This ensures seamless and secure access to the required accounts across different functionalities.

## **Parameters**

Take a look at the configuration options for the component. Parameters supported by [Double Braces expressions](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/overview) are marked with `(DB)`.

{% hint style="info" %}
Depending on the account type selected in the **Account Type** parameter, additional configuration parameters may be activated in the form. These parameters can support [Double Braces](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/overview), and when they do, the field in the form will [include the `{ }` symbol](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/double-braces-autocomplete).
{% endhint %}

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Account Name</strong> <code>(DB)</code></td><td>The name of the account to be stored.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Account Type</strong></td><td><p>The type of account to be stored. Depending on the type, new parameters required for the account are activated in the form. <a href="https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/accounts#accounts-type">Learn more about the configuration of each account type</a>. </p><p>Supported accounts: </p><ul><li><strong>API Key</strong> </li><li><strong>AWS Role</strong> </li><li><strong>AWS V4</strong> </li><li><strong>Basic</strong> </li><li><strong>Certificate Chain</strong> </li><li><strong>Custom Auth Header</strong> </li><li><strong>Google Key</strong> </li><li><strong>NTLM</strong> </li><li><strong>OAuth Bearer Token</strong> </li><li><strong>Private Key</strong> </li><li><strong>Public Key</strong> </li><li><strong>Secret Key</strong> </li><li><strong>SMTP Auth And Properties</strong></li></ul></td><td>Basic</td><td>String</td></tr><tr><td><strong>Scoped</strong></td><td>When active, the stored account is isolated from other subprocesses. In this case, the subprocesses see their own version of the stored account data.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the “success” property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>

## **Usage example**

Suppose you need to authenticate to a database with a Basic credential. In this case, you need to perform the following steps:

1. Configure the **Store Account** to create these credentials to be used in the [**DB V2**](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/structured-data/db-v2) connector.
2. Connect the **DB V2** connector and configure the data of the database to be accessed.
3. Activate the **Use Dynamic Account** parameter in the **DB V2** connector configuration form. Then, enter the account name in the **Account Name** parameter.

Once you have completed the configuration steps, you can use dynamic access to this database.