-
Notifications
You must be signed in to change notification settings - Fork 85
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
Cannot set both public read access & access policy on the same container #197
Comments
Workaround: do not use access policies with public read access, but generate a SAS without using access policies. The solution is less flexible (can't revoke or extend accesses to contributors), but it works. |
Yep, that's a bug! The same REST operation controls both ACLs and the access level, but we don't preserve both pieces of information when setting either of them. |
Fix has been merged into master for 1.3.0. |
The changed access level can’t be saved for one blob container, so create the new bug #380 which is related to this issue. |
This is still broken for me after updating to 1.3.0. Specifically, the scenario in #317 Changing container Access Policies sets Public Access Level to "Private" which was closed as a duplicate of this issue. About info:
Should I file a new issue, or will this one be reopened? |
I've reopened the issue. Apologies for not actually fixing. We'll be releasing a hotfix ASAP. |
1.3.1 notification was sent out last night. That version contains the full fix for this bug. I am now closing this issue. |
Storage Explorer Version: 1.1.0
Platform: Windows
Architecture: ia32
Build Number: 20180507.1
Commit: bcc8990d
Steps to Reproduce:
OR
Expected Experience:
You should be able to have both an access policy (to let contributors manage files in your container) and public read access enabled (to let anonymous users be able to access the files) on your container.
Actual Experience:
The text was updated successfully, but these errors were encountered: