Open juwalter opened 1 year ago
I think we may not support this way right now. now we only support ClientCredsTokenProvider and MsiTokenProvider for abfs.
@Jackson-Wang-7 thank you for the quick feedback
@juwalter If you are interested, you can contribute relevant code implementations. It doesn't seem too difficult.
@Jackson-Wang-7 - yes, we are looking into it!
juwalter this is a question better suitable for alluxio.io/slack #troubleshooting channel. Greg (Email: greg.palmer@alluxio.com @gregpalmr) has more information on Azure SAS token, feel free to contact him directly.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.
/assign @iRevive
/assign @juwalter
I have created a PR for this at https://github.com/Alluxio/alluxio/pull/17583
Page
https://docs.alluxio.io/os/user/stable/en/ufs/Azure-Blob-Store.html https://docs.alluxio.io/os/user/stable/en/ufs/Azure-Data-Lake-Gen2.html
maybe also: https://docs.alluxio.io/os/user/stable/en/ufs/Azure-Data-Lake.html
Summary
Above page describes how to configure Azure Blob and Data Lake Gen2 as "Storage Integration"; they include instructions for using "Shared Key", "OAuth 2.0 Client Credentials", and "Azure Managed Identities" for authentication. However, "SAS token" is missing on both, while - in theory - this should be possible according to:
I have tried like so:
and also (blob.core.windows.net instead of dfs.core.windows.net and wasb instead of abfs)
blob.core.windows.net/wasb result in error message after running into a timeout:
this looks like it is falling back to MSI (managed identity) authentication (since
169.254.169.254
only responds from inside a VM running in Azure)dfs.core.windows.net and abfs result in a non-descript, general error
I wonder if this can be done?