-
Type: Investigation
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Connectivity
-
None
-
3
-
Not Needed
-
Iteration Edmontonia
Keytar is officially archived and not being maintained. VSCode is removing the keytar shim that we rely on for storing credentials. They have their own SecretStorage API we should switch over to.
This ticket involves investing:
- How our connection storage currently works in VSCode. Here is an entry point: https://github.com/mongodb-js/vscode/blob/51326d90494c3d83aa4871591a1d9c2457e45853/src/connectionController.ts#L175
- How we migrate from keytar to the SecretStorage API (this will require a release).
- How we handle when someone updates to the new version of our extension without the migration. This would mean they didn't update to the version we release with a migration from keytar to the SecretStorage API before keytar is removed from VSCode.
- How our error handling and logging work in these situations.
- If there are any things we should consider or account for with the SecretStorage API. For instance error handling and logging.
Update the description of the existing ticket VSCODE-435 with finds and plan of action. If it requires multiple tickets, create those tickets as well.
- is depended on by
-
VSCODE-435 Remove keytar usage, use VSCode's SecretStorage API
- Closed
- is related to
-
VSCODE-184 Move from keytar to Electron safeStorage
- Closed