VS Code SAS Extension - all files/folders visible, even ones without access

[jmacs203]

Describe the bug

When using the SAS Extension for VS Code, the files and folders for the user's NFS mount shows ALL the files and folders, even the ones the user doesn't have access to. This could be viewed as a security risk.
In the same environment, in SAS Studio, the user can only see their files and folders and not the ones they don't have access to.

Steps to reproduce

1. Using VS Code with the SAS Extension, check under "SAS Server" and you will see files/folders the user doesn't have access to

2. In SAS Studio, the user will only see the files/folders they have access to.

3. The way to restrict the user from accessing the folders is to change the "fileNavigationRoot" to CUSTOM in SAS Environment Manager, and set the fileNavigationCustomRootPath to be the path for the NFS mount/SAS Server.

(Please reach out to @jmacs203 or @scottdover to see the screenshots from SAS Studio and VS Code using the SAS Extension.)

SAS code (if applicable)

Expected behavior

No response

Screenshots

No response

Client OS

No response

Extension version

1.18.0

SAS version

2025.12 Stable

Additional context

No response

[scottdover]

Hey @jmacs203 . There are a couple ways to manage fileNavigationRoot.

For SAS studio, you can set those in Configuration > SAS Studio. See...

My best guess is that this is the way things are currently setup in your environment.

For the SAS extension, which doesn't have access to SAS Studio configuration, you'll have to specify fileNavigationCustomRootPath and fileNavigationRoot on the compute context itself. See https://sassoftware.github.io/vscode-sas-extension/Configurations/Profiles/additional#sas-server-file-navigation-root-settings for more information.

If things are setup on the compute context, and you're still having issues, let me know :)

[jmacs203]

Hello Scott (@scottdover),
The customer did set the fileNavigationRoot to CUSTOM and set the fileNavigationCustomRootPath and this restricted their access in VS Code using the SAS Extension. The issue that came up is in SAS Studio, the user can only see their home folder, while in VS Code using the SAS Extension, the user can see all of the folders (even the ones they don't have access to).
Example:
Say the fileNavigationCustomRoot path is set to /home and the /home directory has folders for John, Mary, Angela and Tom.
Using VS Code with the SAS Extension, each user would see all the folders for the other users, even though they don't have access to them.
In SAS Studio itself (same Viya system), the users will only see and access their own folders and not see the folders of the other users.