Stop vs code trying to auto log in to all workspace folder

To prevent VS Code from attempting to automatically log in to all workspace folders when using the InterSystems ObjectScript extension, you can adjust the configuration settings. The InterSystems Server Manager extension facilitates managing server connections, including signing in and storing credentials securely.

1. Disable Automatic Syncing of Local Changes:

   • Update the objectscript.syncLocalChanges setting in your workspace or user settings. Set it to "none" to prevent automatic synchronization of changes to the server.
   • This ensures no unintended login attempts are made to synchronize files automatically 12.

2. Control Login Behavior for Specific Workspaces:

   • Define individual workspace configurations in .code-workspace files. Use these to specify only individual folders that require server access. For example:

     {
       "folders": [
         {
           "name": "SpecificServerNamespace",
           "uri": "isfs://server:namespace/"
         }
       ],
       "settings": {}
     }
     

   • This setup prevents global login attempts unless the specific workspace is explicitly opened 34.

3. Work with Temporary Credentials:

   • When prompted for a password during server sign-in, select "use for this session only" instead of saving credentials. This limits the scope of logged-in servers to the current session only and avoids retained credentials being used for unintended logins 56.

4. Sign-out and Manage Trusted Extensions:

   • Regularly manage signed-in accounts from the VS Code Accounts menu. You can sign out of any account to ensure the credentials are not auto-retrieved on subsequent VS Code launches. Additionally, restrict or manage extension access to InterSystems Server Credentials 5.

Using these approaches, you should be able to control when and how InterSystems connections are established when working with multiple workspaces in VS Code.

Sources:

When you launch VS Code I wonder if what's happening is that it's reopening whichever workspace was open at the time you last exited VS Code. To test this theory please use the "Close Workspace" option from the File menu before you exit from VS Code. Then the next time you launch VS Code do you still get the sign-in permission request?

Also, are you editing server-side (i.e. the old Studio paradigm), or client-side? And is your desktop Windows or macOS or a Linux variant?

This is an intentional design decision. We think it's a better user experience to prompt for login at the start, and after login we cache some information about your server-namespace environment that is used throughout the session. You can get the behavior you want by having separate workspaces for the folders that you don't usually use together. Then when you open one of them you'll only be prompted for the server connection for that one. You can also consider putting the credentials in plain text in the intersystems.servers block. Then you'll never be prompted. This isn't secure though.

Mark, I found that the latest realease was causing VScode to be too slow when loading and it became unusable due performace issues.   We downgraded the VS code objecscipt extension from 3.6.0 to 3.4.0 and it resolved the issue. Please note you may have to create a new connection since the update also create issues with cached credentials.