Incorrect behavior of granting access for the extension to existing authentication session using Manage Trusted Extensions functionality #227694
Labels
authentication
Issues with the Authentication platform
bug
Issue identified by VS Code Team member as probable bug
Milestone
Does this issue occur when all extensions are disabled?: This issue occurs with VS Code functionality FOR the extensions.
Steps to Reproduce:
Actual Result:
Grant access to My Provider for My Extension... (1) is still available in the Accounts menu, even though access has been granted:
Expected Result:
Consequences:
Since VS Code doesn’t provide a direct API to detect when the extension is checked/unchecked in the "Manage Trusted Extensions" dialog, it is impossible to work with authentication correctly.
While both, user account and Grant access to My Provider for My Extension... (1) are available in the Accounts menu, it allows the possibility to sign in under two accounts, even if { supportsMultipleAccounts: false } was passed during registering the Authentication Provider, using
To reproduce this behavior follow these steps:
The text was updated successfully, but these errors were encountered: