Provide the ability to restrict the ability to download/export data from the libraries view

[hyweldaniels]

Is your feature request related to a problem? Please describe.

The extension allows users to easily and quickly download data by right-clicking a table within the libraries view. However for some this is seen as a security concern, since the extension is open source and so there is often little way of preventing users from installing and using it.

Describe the solution you'd like

A configurable option that will disable the download option

Describe alternatives you've considered

I tested manually removing the appropriate snippet in package.json and then reloading the extension. This worked and removed the download option entirely, but is not really a feasible solution for many.

Additional context

No response

SAS version

Viya 4

Sensitive information

• I have confirmed that this feature request contains no sensitive information

[cjdinger]

While not weighing on the feasibility or value of this UI change/config, I will say that this is something that comes up a lot in client applications like this. "Provide an option to hide a capability that the end user would otherwise have ability to use", such as download data, view certain content, etc. Hiding the feature doesn't secure it, as the underlying APIs and user access would still allow a determined user to accomplish it. Clear company policy and/or permissions at the data/server level are the proper answer for these. In fact, providing the option can provide a false impression that the data/action is now secured, simply because it's harder to do.

[BenGow]

100%. However what we're looking for is download data to be blocked from the user based on the server side configuration of the connecting user role. We've prevented download via SAS Studio for these users but the VS code extension facilitates an Opensource path to circumvent the security model and download data that the user has access to.

I had some discussions at Innovate last year about the concept of application aware compute contexts for securing SAS Studio users across client applications. Perhaps that can be explored to track when the connection is via Studio vs VS code?