mirror of
https://github.com/microsoft/vscode.git
synced 2026-04-26 03:29:00 +01:00
e5079d8a05
Bascally, we reach into the old location in secret storage and if we find sessions (with a refresh token) we seed that in the MSAL world. We do this one time... unless they switch back to the old world and then switch to the new world. This has two different behaviors depending on if the Broker is used: * If the broker is not used, this does what you might expect. It makes it seem totally transparent to the user that something has changed. All sessions get migrated over and the user is still logged in to what they were previously. * If the broker is used... you don't get automatically logged in _unless_ you have already logged in to that account at the OS level. So this helps skip the "VS Code access layer" outlined in `accountAccess.ts`. Not as good as the previous bullet, but this is the best we can do in the broker world. In time, we can remove this migration along with the old way of doing things.
Microsoft Authentication for Visual Studio Code
Notice: This extension is bundled with Visual Studio Code. It can be disabled but not uninstalled.
Features
This extension provides support for authenticating to Microsoft. It registers the microsoft Authentication Provider that can be leveraged by other extensions. This also provides the Microsoft authentication used by Settings Sync.
Additionally, it provides the microsoft-sovereign-cloud Authentication Provider that can be used to sign in to other Azure clouds like Azure for US Government or Azure China. Use the setting microsoft-sovereign-cloud.endpoint to select the authentication endpoint the provider should use. Please note that different scopes may also be required in different environments.