Azure Data Lake Storage Gen 2 OAuth2 Account
In this article
Overview
Use this account type to connect Hadoop Snaps with data sources that use Azure Data Lake Storage Gen 2 OAuth2 accounts.
Prerequisites
- None.
Limitations and Known Issues
- None.
Account Settings
All fields are required.
Parameter Name | Data Type | Description | Default Value | Example |
---|---|---|---|---|
Label | String | Unique name for the account. | N/A | ADLS Gen2 OAuth2 Account |
Account name | String | The name of the ADLS Gen 2 storage account that you created in the Azure portal. | N/A | adlsgen2oauth2test1 |
Endpoint | String | The endpoint provided by Microsoft Azure. The protocols supported are HTTPS, ADL, and ADLS. | dfs.core.windows.net | dfs.core.windows.net |
Tenant ID | String | The Directory ID of the Azure Active Directory. You must retrieve this information from your Azure account. For information on creating a Tenant ID in Azure, see Quickstart: Create a new tenant in Azure Active Directory. | N/A | 4464acc4-0c44-46ff-560c-65c41354405f |
Access ID | String | The Application ID of the application in the Azure Active Directory. You must retrieve this information from your Azure Active Directory Application. For information on working with access IDs, see How to: Use the portal to create an Azure AD application and service principal that can access resources. | N/A | N/A |
Secret Key | String | The authentication key for accessing the Azure Active Directory. You must retrieve this information from your Azure Active Directory Application. For information on secret keys, see How to: Use the portal to create an Azure AD application and service principal that can access resources. | N/A | N/A |
Troubleshooting
Error Message | Reason | Resolution |
---|---|---|
Failed to validate account: An error occurred while getting a new access token. | Bad Request The Tenant ID, Access ID, or Secret Key details are incorrect. | Check the account information and try again |
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.