microsoft / microsoft/AzureStorageExplorer

manage acl when folder permission is set to rws

Open
#9,089 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:gear: adls gen2 :triumph: easy
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.43.0

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20260407

Platform

Windows

OS Version

Windows 11

Bug Description

Seems like storage explorer can not handle rws permission set on folder when selecting "manage acl" on folder? Get following error

{
"name": null,
"message": ""{\n \"name\": \"RangeError\",\n \"message\": \"toRolePermissions() Invalid role permissions string rws\",\n \"stack\": \"RangeError: toRolePermissions() Invalid role permissions string rws\\n at toRolePermissions (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:105:70297)\\n at toPermissions (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:105:71123)\\n at C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:112:7689\\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\\n at async Object.withSpan (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:81:7604)\\n at async bh.runOperation (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:44:5875)\\n at async bh.getAccessControl (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:114:5886)\\n at async managePathAcl (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:114:18982)\\n at async Azure.Storage.AdlsGen2.managePathPermissions (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:116:13946)\\n at async Provider.executeOperation (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\out\\\\app\\\\node\\\\NodeProcessHostProxy.js:3:2758)\"\n}""
}

Resource Types

No response

Authentication Method

None

Connection Type

None

Steps to Reproduce
  1. Launch storage explorer.
  2. Right click on folder with rws permission set and select "manage acl".
Actual Experience

Following error is displayed Failed to get permissions for 'path' with following details.

{
"name": null,
"message": ""{\n \"name\": \"RangeError\",\n \"message\": \"toRolePermissions() Invalid role permissions string rws\",\n \"stack\": \"RangeError: toRolePermissions() Invalid role permissions string rws\\n at toRolePermissions (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:105:70297)\\n at toPermissions (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:105:71123)\\n at C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:112:7689\\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\\n at async Object.withSpan (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:81:7604)\\n at async bh.runOperation (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:44:5875)\\n at async bh.getAccessControl (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:114:5886)\\n at async managePathAcl (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:114:18982)\\n at async Azure.Storage.AdlsGen2.managePathPermissions (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\node_modules\\\\@storage-explorer\\\\adls2-extension\\\\dist\\\\src\\\\index.js:116:13946)\\n at async Provider.executeOperation (C:\\\\temp\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\out\\\\app\\\\node\\\\NodeProcessHostProxy.js:3:2758)\"\n}""
}

Expected Experience

No response

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with an ADLS Gen2 folder whose permission string is rws, then trace the reported toRolePermissions(), toPermissions(), getAccessControl(), and managePathAcl() entry points in the bundled adls2-extension path. Done means Manage ACL opens for that folder without the invalid-permissions error and the existing permissions are handled correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
authorization, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.