Connectors and Connections > Data Ingestion and Replication connection properties > Google Cloud Storage V2 connection properties
  

Google Cloud Storage V2 connection properties

Create a Google Cloud Storage V2 connection to securely read data from or write data to Google Cloud Storage files.
You can use a Google Cloud Storage V2 connection to specify sources and targets in mappings and mapping tasks.

Prerequisites for Service Account authentication

Before you configure a Google Cloud Storage V2 connection to use Service Account authentication, complete the following prerequisite tasks.
  1. 1Ensure that you have a Google service account to access Google Cloud Storage.
  2. 2Ensure that you have the client email, project ID, and private key values for the service account. Enter these details when you create a Google Cloud Storage V2 connection.
  3. 3Enable the Google Cloud Storage JSON API for your service account. Google Cloud Storage V2 Connector uses the Google API to integrate with Google Cloud Storage.

Connect to Google Cloud Storage V2

Let's configure the Google Cloud Storage V2 connection properties to connect to Google Cloud Storage.

Connection details

The following table describes the Google Cloud Storage V2 connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run tasks.

Authentication types

You can connect to Google Cloud Storage with a service account key or with Workload Identity Federation (WIF).
The following table describes the authentication types that you can select in the connection:
Authentication Type
Description
Service Account
Authenticate with the credentials in a Google service account key file.
WIF (Client Credentials)
Authenticate with WIF and an identity provider that uses the OAuth 2.0 client credentials grant. The connection doesn't require a user to sign in. You can also impersonate a service account and access Google Cloud Storage resources in a different project. You can configure Microsoft Entra ID as the identity provider.
The default is Service Account.
After you select an authentication type, configure the properties for that type.

Proxy server settings

If your organization uses an outgoing proxy server to connect to the Internet, the Secure Agent connects to Informatica® Intelligent Data Management Cloud™ (IDMC) through the proxy server.
You can configure the Secure Agent to use the proxy server on Windows and Linux. You can connect to Google Cloud Storage through an authenticated or unauthenticated HTTP proxy server.
To configure the proxy settings for the Secure Agent, perform the following tasks:

Configure proxy settings for NTLM authentication

You can use a proxy server that uses NTLM authentication to connect to Google Cloud Storage.
To configure the proxy settings for NTLM authentication, perform the following steps:
  1. 1In Administrator, select Runtime Environments.
  2. 2Select the Secure Agent for which you want to configure from the list of available Secure Agents.
  3. 3In the upper-right corner, click Edit.
  4. 4In the System Configuration Details section, select the Type as DTM for the Data Integration Server.
  5. 5Edit the JVMOption1 and add the following value:
  6. -Dhttp.auth.ntlm.domain=<domain name>
  7. 6Select the Type as Platform for the Data Integration Server.
  8. 7Edit the INFA_DEBUG property and add the following value:
  9. -Dhttp.auth.ntlm.domain=<domain name>
  10. 8Click Save.
  11. 9Restart the Secure Agent.