Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container Access Level not working #151

Closed
yss14 opened this issue Feb 7, 2019 · 2 comments
Closed

Container Access Level not working #151

yss14 opened this issue Feb 7, 2019 · 2 comments
Labels
enhancement New feature or request legacy Legacy Azurite V2 and previous versions v3.3 Issues to fix in v3.3

Comments

@yss14
Copy link

yss14 commented Feb 7, 2019

Hi

Is the container access level currently supported by azurite?
When creating a new container with the node-sdk the default access level should be private. However, the files within this container are public accessible without any SAS token.
When changing the AZURE_STORAGE_CONNECTION_STRING to a real azure blob storage account, everything is working like expected. The files are not public accessible.

@XiaoningLiu
Copy link
Member

Azurite is more focusing on positive features right now. Negative cases are not fully aligned yet.

@XiaoningLiu XiaoningLiu added the enhancement New feature or request label Feb 14, 2019
@XiaoningLiu
Copy link
Member

Hi @yss14 please try with Azurite v3 which has fully container access level support. Will close this issue!

@XiaoningLiu XiaoningLiu added the legacy Legacy Azurite V2 and previous versions label Nov 12, 2019
@vinjiang vinjiang added the v3.3 Issues to fix in v3.3 label Jan 6, 2020
@vinjiang vinjiang closed this as completed Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request legacy Legacy Azurite V2 and previous versions v3.3 Issues to fix in v3.3
Projects
None yet
Development

No branches or pull requests

3 participants