User Workspace on Shared Servers: avoid the creation.

Hi Team,

As commented with Carlos and Juan, we have detected a problem with LM Workspace on Shared Environment.

Those environments are strongly protected to prevent users from accessing other users' data. Then from the security perspective we would like to avoid that any Workspace can be created on those servers. Especially the called "Workspace SQL Server RunQuery", that in your wiki specifies that lmwin login is used.

If users are not given instance roles, the problem is somewhat minimized, but there would still be a security flaw if a user misusing LM and knowing that lmwin can access other databases attempts to do so.

We have escalated this issue to our L3 Support to obtain their agreement and they think the same:

[Jose Francisco] - I fully agree on that, Observality team should have a mechanism to identify if it's a Shared Environment or not, to avoid deploying this on them.

Please, can you check if it's possible to avoid creating Workspaces on Shareds?

Thanks in advance!

P.S.: I don't know if Oracle team has the same problem, so I speak from SQL Server side.