mirror of
https://github.com/Microsoft/vscode
synced 2024-07-17 02:57:19 +00:00
d5c2817e69
So, when you make a new session in the Microsoft Identity stack, depending on the scopes you pass in you might get: * A token with a name & email * A token with just a name Additionally, Microsoft has like 3-4 concepts of essentially an "id" but depending on what you're trying to access, you might get a different value. This historical behavior leads to 2 awkward things: 1. The account menu shows two accounts, one with name & email, one with just email. 2. The account menu shows two of the same accounts, but their underlying id is different So, to fix this, we're just gonna lean on the labels. In other words, if there are two accounts that share the same label, then they will be grouped together. The previous behavior was hurting the Azure Account folks and the Q# folks and with this change, I believe they both should be happy. Interestingly enough, when I inherited this code, it use to do this, but I changed it to use the id as that seemed "more correct"... so it a way, this is reverting a change I did a while back. Fixes https://github.com/microsoft/vscode/issues/184218 |
||
|---|---|---|
| .. | ||
| media | ||
| src | ||
| .vscodeignore | ||
| extension-browser.webpack.config.js | ||
| extension.webpack.config.js | ||
| package.json | ||
| package.nls.json | ||
| README.md | ||
| tsconfig.json | ||
| yarn.lock | ||
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.