Configure role-based access control for Microsoft Azure Data Lake Storage Gen2
Configure role-based access control for Microsoft Azure Data Lake Storage Gen2
Before you use Microsoft Azure Data Lake Storage Gen2 to stage files, perform the following tasks:
Create a storage account to use with Microsoft Azure Data Lake Storage Gen2 and enable
Hierarchical namespace
in the Azure portal.
You can use role-based access control to authorize the users to access the resources in the storage account. Assign the Contributor role or Reader role to the users. The contributor role grants you full access to manage all resources in the storage account, but does not allow you to assign roles. The reader role allows you to view all resources in the storage account, but does not allow you to make any changes.
To add or remove role assignments, you must have write and delete permissions, such as an Owner role.
Register an application in Azure Active Directory to authenticate users to access the Microsoft Azure Data Lake Storage Gen2 account.
You can use role-based access control to authorize the application. Assign the Storage Blob Data Contributor or Storage Blob Data Reader role to the application. The Storage Blob Data Contributor role lets you read, write, and delete Azure Storage containers and blobs in the storage account. The Storage Blob Data Reader role lets you only read and list Azure Storage containers and blobs in the storage account.
Create an Azure Active Directory web application for service-to-service authentication with Microsoft Azure Data Lake Storage Gen2.
Ensure that you have superuser privileges to access the folders or files created in the application using the connector.
To read
and write
complex files, set the JVM options for type DTM to increase the -Xms and -Xmx values in the system configuration details of the Secure Agent to avoid java heap space error. The recommended -Xms and -Xmx values are 512 MB and 1024 MB respectively.