• Default Credential Provider Chain: (Default) Select this option to use the "default" credentials provider chain that is provided in the AWS SDK. For information about the standard mechanism that AWS client-side automation tools use to obtain user credentials, see New and Standardized Way to Manage Credentials in the AWS SDKs.

• Access Keys: Select this option to use access keys which are long-term credentials for an IAM user or the AWS account root user. Access keys are created in pairs that consist of the following (displayed as additional options):

• Blob Storage Service: (Default) Component uses Microsoft Azure's Blob-specific APIs to interact with the selected storage account and container. For more information, see Introduction to Azure Blob Storage.

• ADLS File System Service: Component uses Microsoft Azure's Data Lake Storage Gen2 hierarchical namespace-specific APIs to interact with the selected storage account and container. For more information, see Azure Data Lake Storage Gen2 hierarchical namespace.

• Storage Shared Access Keys: (Default) Azure generates two 512-bit storage account access keys when you create a storage account. These keys can be used to authorize access to data in your storage account through Shared Key authorization. When selected, the following additional option is displayed:

• Azure Active Directory Service Principal With Client Secret: Customer applications, which embed the Azure Storage Component, can be integrated with the Microsoft identity platform by registering it with an Azure Active Directory tenant. After this, a client secret can be generated from the registered application and it can be used for authentication. For more information, see Microsoft’s How to page. Actian Data Platform COPY VWLOAD directly supports this type of registration and authentication. When selected, the following additional options are displayed:

• Active

• Passive (default)

• EXPLICIT - (default) Explicit FTPS is the newer method of FTPS transfer and is supported by majority of FTP servers. In Explicit FTPS the client "explicitly" requests the server to create a secured session, using SSL/TLS.

• IMPLICIT - Implicit FTPS was the first method created to encrypt data sent via FTP and in this connection the SSL encryption is “implied”. As soon as a connection is established between the FTPS client and the file transfer server, both command and data channels are automatically protected with SSL encryption. Thus the entire FTP session is encrypted, in contrast to flexibility you have when using explicit FTPS. However, implicit FTPS is considered a deprecated protocol, meaning that it not the current standard.

• Use path in environment variable (GOOGLE_APPLICATION_CREDENTIALS): (Default) Instructs the component to find the service account key file using the GOOGLE_APPLICATION_CREDENTIALS environment variable. If the environment variable is set, then its value is expected to be the path to the file. If the environment variable is not set, then an error occurs.

• Provide path to service account key file: Displays the Service Account Key File property to specify the complete path of the service account key file.

• Directly provide service account key: Allows you to directly provide the service account keys. This is a non-file-based authentication method. When selected, the following additional properties are displayed:

• None (default)

• HTTP - Routes only HTTP/HTTPS traffic between your device and the internet.

• SOCKS5 - A more versatile proxy that supports all internet traffic types (HTTP, FTP, etc.) with no traffic modification, ideal for diverse applications.