[GitHub] [camel] ank19 commented on pull request #9567: Azure Data Lake - CAMEL-19152 additional file client header field + CAMEL-18636 additional auth options

["ank19 (via GitHub)" <gi...@apache.org>]

ank19 commented on PR #9567:
URL: https://github.com/apache/camel/pull/9567#issuecomment-1473658034

   @oscerd - Sure, for me it's fine to drop the validation method, I'm just not sure what is "common" or "usual" in the project. I'm removing it and updating the PR accordingly.
   
   Concerning the Data Lake setup, what I did is basically creating a standard Azure storage account, then, on the overview page, setting Hierarchical namespace to "enabled", which starts that sort of a migration process to Data Lake Gen2. Then I tried three authentication methods for creation of a new file and appending data to that file, specifying an account name and:
   1.  Within "Security + networking / Shared access signature": Generate a new SAS with the appropriate permissions and constraints set, then using the "Signature" to set the "sasSignature" as configuration parameter on the component (the thing starting with "?...").
   2. Within "Security + networking / Access keys": Using one of the two provided tokens to set "accountKey".
   3. Creating an app registration on Azure AD, and then under "Certificates & secrets", creating a new client secret, using the "Value" from that page as "clientSecret", and from the overview page the "Application (client) id" as "clientId" as well as "Directory (tenant) id" as "tenantId". Afterwards, I configured on the storage account, in "Access Control (IAM)", that the app registration just created gets the role "Contributor" for instance. Afterwards I used the Microsoft Storage Explorer to "Propagate Access Control Lists..." on a newly created container, so that the ACLs get applied.
   
   I created a Zulip account - If you like you can try to contact me there, too. However, I might be online from time to time only.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org