# Secret Manager - Access task

> [!WARNING]
>
> **Preview
> --- BigQuery Connector**
>
>
> This feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the
> [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

The **Secret Manager - Access** task lets you access [secret versions](https://docs.cloud.google.com/secret-manager/docs/overview.md.txt#version) that are stored in Cloud Secret Manager from your integration. Accessing a secret version returns the content of that [secret](https://docs.cloud.google.com/secret-manager/docs/overview.md.txt#secret) along with additional metadata about the secret version such as, labels and replication information.

[Cloud Secret Manager](https://docs.cloud.google.com/secret-manager/docs/overview.md.txt) is a Google Cloud service that allows you to store, access, and manage sensitive configuration data such as, database passwords, API keys, or TLS certificates that are required by an application during runtime.

## Before you begin

Ensure that you perform the following tasks in your Google Cloud project before configuring the **Secret Manager - Access** task:

1. Enable the Secret Manager API (`secretmanager.googleapis.com`).


   [Enable the Secret Manager API](https://console.cloud.google.com/apis/enableflow?apiid=secretmanager.googleapis.com)

   <br />

2. Create an [authentication profile](https://docs.cloud.google.com/application-integration/docs/configuring-auth-profile#createAuthProfile). Application Integration uses an authentication profile to connect to an authentication endpoint for the **Secret Manager - Access** task.

   > [!NOTE]
   > **Note:** If you're creating an authentication profile of [Service account](https://docs.cloud.google.com/application-integration/docs/configure-authentication-profiles.md.txt#service-account) type, then ensure that the service account is assigned with the IAM role that contains the following IAM permission(s):
   > - `secretmanager.secretAccessor`
   >
   > To know about IAM permissions and the predefined IAM roles that grant them, see [IAM permissions reference](https://docs.cloud.google.com/iam/docs/roles-permissions.md.txt).
   >
   > For information about granting additional roles or permissions to a service account, see [Granting, changing, and revoking access](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).

## Configure the Secret Manager - Access task

1. In the Google Cloud console, go to the **Application Integration** page.

   [Go to Application Integration](https://console.cloud.google.com/integrations)
2. In the navigation menu, click **Integrations** .


   The **Integrations** page appears listing all the integrations available in the Google Cloud project.
3. Select an existing integration or click **Create integration** to create a new one.


   If you are creating a new integration:
   1. Enter a name and description in the **Create Integration** pane.
   2. Select a region for the integration.

      > [!NOTE]
      > **Note:** The **Regions** dropdown only lists the regions provisioned in your Google Cloud project. To provision a new region, click **Enable Region** . See [Enable new region](https://docs.cloud.google.com/application-integration/docs/enable-new-region.md.txt) for more information.

   3. Select a service account for the integration. You can change or update the service account details of an integration any time from the **Integration summary** pane in the integration toolbar.

      > [!NOTE]
      > **Note:** The option to select a service account is displayed only if you have enabled integration governance for the selected region.

   4. Click **Create** . The newly created integration opens in the *integration editor*.


4. In the *integration editor* navigation bar, click **Tasks** to view the list of available tasks and connectors.
5. Click and place the **Secret Manager - Access** element in the integration editor.
6. Click the **Secret Manager - Access** element on the designer to view the **Secret Manager - Access** task configuration pane.
7. Go to **Authentication** , and select an existing authentication profile that you want to use.

   Optional. If you have not created an authentication profile prior to configuring the task, Click **+ New authentication profile** and follow the steps as mentioned in [Create a new authentication profile](https://docs.cloud.google.com/application-integration/docs/configuring-auth-profile#createAuthProfile).
8. Go to **Task Input** , and configure the displayed inputs fields using the following [Task input parameters](https://docs.cloud.google.com/application-integration/docs/gcp-tasks/configure-secretmanager-access-task.md.txt#params) table.

   Changes to the inputs fields are saved automatically.

## Task input parameters


The following table describes the input parameters of the **Secret Manager - Access** task:

| Property | Data type | Description |
|---|---|---|
| Projectsid | String | Your Google Cloud project ID. |
| Secretsid | String | The ID of your [secret](https://docs.cloud.google.com/secret-manager/docs/overview.md.txt#secret). |
| Versionsid | String | The version ID or *alias* of your [secret](https://docs.cloud.google.com/secret-manager/docs/overview.md.txt#version). You can access the latest version of a secret by specifying <var translate="no">latest</var> as the version ID. |

## Task output

The **Secret Manager - Access** task returns the response `payload.data`, containing the base64-encoded content of the secret version. You must decode the base64-encoded value to get the output string.

> [!TIP]
> **Tip:** You can base64-encode or decode data using the **base64** command on Linux or macOS, or the **Base64.exe** command on Windows. Programming and scripting languages typically include libraries for base64-encoding. For command-line examples, see [Decode base64](https://docs.cloud.google.com/text-to-speech/docs/base64-decoding.md.txt#linux) in the Cloud Text-to-Speech documentation.

<br />

## Error handling strategy


An error handling strategy for a task specifies the action to take if the task fails due to a [temporary error](https://docs.cloud.google.com/application-integration/docs/error-handling.md.txt). For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see [Error handling strategies](https://docs.cloud.google.com/application-integration/docs/error-handling-strategy.md.txt).

## Quotas and limits

For information about quotas and limits, see [Quotas and limits](https://docs.cloud.google.com/application-integration/docs/quotas.md.txt).

## What's next

- Add [edges and edge conditions](https://docs.cloud.google.com/application-integration/docs/edge-overview).
- [Test and publish](https://docs.cloud.google.com/application-integration/docs/test-publish-integrations.md.txt) your integration.
- Configure a [trigger](https://docs.cloud.google.com/application-integration/docs/how-to-guides#configure-triggers).
- Add a [Data Mapping task](https://docs.cloud.google.com/application-integration/docs/data-mapping-task).
- See [all tasks for Google Cloud services](https://docs.cloud.google.com/application-integration/docs/how-to-guides#configure-tasks-for-google-cloud-services).