A tarefa Secret Manager - Access permite acessar versões do secret armazenadas no Cloud Secret Manager a partir da sua integração. O acesso a uma versão do secret retorna o conteúdo desse secret com metadados adicionais, como rótulos e informações de replicação.
O Cloud Secret Manager é um serviço do Google Cloud que permite armazenar, acessar e gerenciar dados de configuração confidenciais, como senhas de banco de dados, chaves de API ou certificados TLS exigidos por um aplicativo durante o tempo de execução.
Antes de começar
Execute as seguintes tarefas no projeto do Google Cloud antes de configurar a tarefa Secret Manager - Access:
Ative a API Secret Manager (secretmanager.googleapis.com).
Criar um perfil de autenticação. A Application Integration usa um perfil de autenticação para se conectar a um endpoint de autenticação para a tarefa Secret Manager - Access.
Configurar a tarefa "Secret Manager: Access"
No console Google Cloud , acesse a página Application Integration.
A página Integrações aparece listando todas as integrações disponíveis no projeto do Google Cloud.
Selecione uma integração ou clique em Criar integração para criar uma.
Caso você esteja criando uma nova integração, siga estas etapas:
Digite um nome e uma descrição no painel Criar integração.
Selecione uma região para a integração.
Selecione uma conta de serviço para a integração. É possível mudar ou atualizar os detalhes da conta de serviço de uma integração a qualquer momento no painel Resumo da integraçãoinfo na barra de ferramentas de integração.
Clique em Criar. A integração recém-criada é aberta no editor de integração.
Na barra de navegação do editor de integração, clique em Tarefas para conferir a lista de tarefas e conectores disponíveis.
Clique e coloque o elemento Secret Manager - Access no editor de integração.
Clique no elemento Secret Manager - Access no designer para ver o painel de configuração da tarefa Secret Manager - Access.
Acesse Autenticação e selecione o perfil de autenticação que você quer usar.
Opcional. Se você não tiver criado um perfil de autenticação antes de configurar a tarefa, clique em + Novo perfil de autenticação e siga as etapas em Criar um novo perfil de autenticação.
Para acessar a versão mais recente de um secret, especifique latest como o ID da versão.
Saída da tarefa
A tarefa Secret Manager - Access retorna a resposta payload.data, que contém o conteúdo codificado em Base64 da versão do secret. É necessário decodificar o valor codificado em base64 para receber a string de saída.
Estratégia de solução de erros
A estratégia de solução de erros para uma tarefa especifica a ação a ser realizada se a tarefa falhar
devido a um erro temporário. Para mais informações sobre como usar uma estratégia de tratamento de erros e conhecer os diferentes tipos de estratégias de tratamento de erros, consulte Estratégias de tratamento de erros.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-25 UTC."],[[["\u003cp\u003eThe \u003cstrong\u003eSecret Manager - Access\u003c/strong\u003e task allows users to retrieve secret versions stored in Cloud Secret Manager directly from within their integrations.\u003c/p\u003e\n"],["\u003cp\u003eBefore using the task, users must enable the Secret Manager API and create an authentication profile that has the required IAM permissions, such as \u003ccode\u003esecretmanager.secretAccessor\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo configure the \u003cstrong\u003eSecret Manager - Access\u003c/strong\u003e task, users will need to select or create an authentication profile and then provide the project ID, secret ID, and the version ID within the task input parameters.\u003c/p\u003e\n"],["\u003cp\u003eThe task's output is a \u003ccode\u003epayload.data\u003c/code\u003e response containing the base64-encoded secret content that users will need to decode to obtain the actual secret value.\u003c/p\u003e\n"],["\u003cp\u003eThe task has an error handling strategy in place to take action if a temporary error happens, as well as having quotas and limits that users should be aware of.\u003c/p\u003e\n"]]],[],null,["# Secret Manager - Access task\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nSecret Manager - Access task\n============================\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThe **Secret Manager - Access** task lets you access [secret versions](/secret-manager/docs/overview#version) that are stored in Cloud Secret Manager from your integration. Accessing a secret version returns the content of that [secret](/secret-manager/docs/overview#secret) along with additional metadata about the secret version such as, labels and replication information.\n\n[Cloud Secret Manager](/secret-manager/docs/overview) 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.\n\nBefore you begin\n----------------\n\nEnsure that you perform the following tasks in your Google Cloud project before configuring the **Secret Manager - Access** task:\n\n1. Enable the Secret Manager API (`secretmanager.googleapis.com`).\n\n\n [Enable the Secret Manager API](https://console.cloud.google.com/flows/enableapi?apiid=secretmanager.googleapis.com)\n\n \u003cbr /\u003e\n\n2. Create an [authentication profile](/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:** If you're creating an authentication profile of [Service account](/application-integration/docs/configure-authentication-profiles#service-account) type, then ensure that the service account is assigned with the IAM role that contains the following IAM permission(s):\n | - `secretmanager.secretAccessor`\n |\n | To know about IAM permissions and the predefined IAM roles that grant them, see [IAM permissions reference](/iam/docs/permissions-reference#search).\n |\n | For information about granting additional roles or permissions to a service account, see [Granting, changing, and revoking access](/iam/docs/granting-changing-revoking-access).\n\nConfigure the Secret Manager - Access task\n------------------------------------------\n\n1. In the Google Cloud console, go to the **Application Integration** page.\n\n [Go to Application Integration](https://console.cloud.google.com/integrations)\n2. In the navigation menu, click **Integrations** .\n\n\n The **Integrations** page appears listing all the integrations available in the Google Cloud project.\n3. Select an existing integration or click **Create integration** to create a new one.\n\n\n If you are creating a new integration:\n 1. Enter a name and description in the **Create Integration** pane.\n 2. Select a region for the integration. **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](/application-integration/docs/enable-new-region) for more information.\n 3. Select a service account for the integration. You can change or update the service account details of an integration any time from the info **Integration summary** pane in the integration toolbar. **Note:** The option to select a service account is displayed only if you have enabled integration governance for the selected region.\n 4. Click **Create** . The newly created integration opens in the *integration editor*.\n\n\n4. In the *integration editor* navigation bar, click **Tasks** to view the list of available tasks and connectors.\n5. Click and place the **Secret Manager - Access** element in the integration editor.\n6. Click the **Secret Manager - Access** element on the designer to view the **Secret Manager - Access** task configuration pane.\n7. Go to **Authentication** , and select an existing authentication profile that you want to use.\n\n 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](/application-integration/docs/configuring-auth-profile#createAuthProfile).\n8. Go to **Task Input** , and configure the displayed inputs fields using the following [Task input parameters](#params) table.\n\n Changes to the inputs fields are saved automatically.\n\nTask input parameters\n---------------------\n\n\nThe following table describes the input parameters of the **Secret Manager - Access** task:\n\nTask output\n-----------\n\nThe **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.\n| **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](/text-to-speech/docs/base64-decoding#linux) in the Cloud Text-to-Speech documentation.\n\n\u003cbr /\u003e\n\nError handling strategy\n-----------------------\n\n\nAn error handling strategy for a task specifies the action to take if the task fails due to a [temporary error](/application-integration/docs/error-handling). 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](/application-integration/docs/error-handling-strategy).\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Add [edges and edge conditions](/application-integration/docs/edge-overview).\n- [Test and publish](/application-integration/docs/test-publish-integrations) your integration.\n- Configure a [trigger](/application-integration/docs/how-to-guides#configure-triggers).\n- Add a [Data Mapping task](/application-integration/docs/data-mapping-task).\n- See [all tasks for Google Cloud services](/application-integration/docs/how-to-guides#configure-tasks-for-google-cloud-services)."]]
