microsoft / microsoft/AzureStorageExplorer
Fail to paste one file from one file share which has 'Storage File Data Privileged Reader' role to one blob container which has 'Storage Blob Data Contributor' role
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.34.0-dev (98)
Build Number: 20240305.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.3(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce
- Launch Storage Explorer -> Check the settings 'Enable Files OAuth Support' and 'Disable Usage Of Keys'.
- Restart Storage Explorer.
- Expand one storage account which has assigned a role 'Storage File Data Privileged Reader' -> File Shares.
- Open one file share -> Copy one file.
- Expand one storage account which has assigned a role 'Storage Blob Data Contributor' -> Blob Containers.
- Open one blob container -> Click 'Paste'.
- Check whether succeeds to paste the file.
Expected Experience
Succeed to paste the file.
Actual Experience
Fail to paste the file.
Additional Context
- Here is the AzCopy log:
a3cd282f-e55c-244b-5c2b-26eb45e09a7d.log - This issue doesn't reproduce if paste one blob from one blob container which has 'Storage Blob Data Reader' role to a file share which has 'Storage File Data Privileged Contributor' role.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the listed Storage Explorer file-share-to-blob-container paste with Files OAuth Support enabled and key usage disabled. Inspect the attached AzCopy log and compare the required roles on both resources; done means the file paste succeeds under the stated permissions and the existing reverse-direction case remains working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authorization, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100