Please enable JavaScript.
Coggle requires JavaScript to display documents.
6 secure - Coggle Diagram
6 secure
-
shared access signatures
best practice
- you shouldn't share storage account keys with external third-party applications
- For untrusted clients, use a shared access signature (SAS)
- allow only the access that the application needs to do the task
-
types
-
allow access to anything that a service-level shared access signature can allow, plus additional resources and abilities
designs
- Clients upload and download data through a front-end proxy service, which performs authentication
- A lightweight service authenticates the client as needed. Then it generates a shared access signature
-
-
Azure Data Lake
-
- role-based access control (RBAC)
- access control lists (ACLs)
- POSIX-compliant
- restrict access to only authorized users,
groups, or service principals
-
-