You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hadoop-tools/hadoop-azure/src/site/markdown/index.md
+13-4
Original file line number
Diff line number
Diff line change
@@ -652,13 +652,17 @@ To know more about how SAS Authentication works refer to
652
652
[Grant limited access to Azure Storage resources using shared access signatures (SAS)](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview)
653
653
654
654
There are three types of SAS supported by Azure Storage:
655
-
-[User Delegation SAS](https://learn.microsoft.com/en-us/rest/api/storageservices/create-user-delegation-sas): Recommended for use with ABFS Driver with HNS Enabled ADLS Gen2 accounts. It is Identity based SAS that works at blob/directory level)
SAS-based authentication works with HNS-enabled ADLS Gen2 accounts
657
+
(recommended for use with ABFS) and is also supported with non-HNS (FNS) Blob
658
+
accounts. However, it is **NOT SUPPORTED** with FNS-DFS accounts.
656
659
-[Service SAS](https://learn.microsoft.com/en-us/rest/api/storageservices/create-service-sas): Global and works at container level.
657
660
-[Account SAS](https://learn.microsoft.com/en-us/rest/api/storageservices/create-account-sas): Global and works at account level.
658
661
659
662
#### Known Issues With SAS
660
-
- SAS Based Authentication works only with HNS Enabled ADLS Gen2 Accounts which
661
-
is a recommended account type to be used with ABFS.
663
+
- SAS Based Authentication works with HNS Enabled ADLS Gen2 Accounts (which
664
+
is a recommended account type to be used with ABFS). It is also supported with
665
+
non-HNS (FNS) Blob accounts. It is **NOT SUPPORTED** with FNS-DFS accounts.
662
666
- Certain root level operations are known to fail with SAS Based Authentication.
663
667
664
668
#### Using User Delegation SAS with ABFS
@@ -1465,7 +1469,12 @@ Once the above properties are configured, `hdfs dfs -ls abfs://container1@abfswa
1465
1469
1466
1470
Following failures are known and expected to fail as of now.
1467
1471
1. AzureBlobFileSystem.setXAttr() and AzureBlobFileSystem.getXAttr() will fail when attempted on root ("/") path with `Operation failed: "The request URI is invalid.", HTTP 400 Bad Request`
1468
-
1472
+
2. If you're using user-delegation SAS authentication:
1473
+
- Listing operation for HNS accounts (on DFS endpoint) works with SAS token supporting either blob or directory
1474
+
scopes (Signed Resource Type as Blob or Directory),
1475
+
though it is intended to work only at the directory scope. It is a known bug.
1476
+
- AzureBlobFileSystem.getFileStatus() is expected to fail at root ("/") path with
1477
+
`Operation failed: "Server failed to authenticate the request.", HTTP 401 Unauthorized Error`
1469
1478
## <aname="testing"></a> Testing ABFS
1470
1479
1471
1480
See the relevant section in [Testing Azure](testing_azure.html).
0 commit comments