Open magodo opened 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.
Author: | magodo |
---|---|
Assignees: | - |
Labels: | `Storage`, `Service Attention` |
Milestone: | - |
@xgithubtriage
@xgithubtriage
This is for dataplane. @seanmcc-msft Would you please help to look?
As I know, all B/T/Q/F rest API to manage ACL , request account shared key credentail. The limitation is not only for table.
Is there any update on this? Official Microsoft documentation doesn't recommend using shared access keys for production environments.
Authorization with Shared Key is not recommended as it may be less secure. For optimal security, disable authorization via Shared Key for your storage account, as described in Prevent Shared Key authorization for an Azure Storage account.
Use of access keys and connection strings should be limited to initial proof of concept apps or development prototypes that don't access production or sensitive data. Otherwise, the token-based authentication classes available in the Azure SDK should always be preferred when authenticating to Azure resources.
This issue seems to be blocking https://github.com/hashicorp/terraform-provider-azurerm/issues/15083 which means anyone using Terraform to manage storage accounts needs to enable shared access keys.
Azure has announced that storage table supports AAD Auth. It does for CRUD on table resource, while it doesn't for the CRUD on the ACL of the table. The portal still uses the shared key authorization for ACL.