Keytar Replacement

[adam-wolfe]

Issue

Due to the sunsetting of the Atom organization, which owned the Keytar project, the original Keytar project has been archived and will not be receiving future updates. This will become an issue for Zowe CLI if vulnerabilities within Keytar are discovered in the future.

Resolution

To ensure that Zowe CLI continues to provide an actively managed solution for secure credential storage, the Zowe CLI Squad will develop a secure credential solution in Rust, based on the original Keytar project. Zowe CLI's Rust Keytar implementation is intended to preserve the same functionality of the original Keytar project and require minimal reworking of existing secure credential storage-related Zowe CLI code.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[traeok]

The Secrets SDK keyring package has been implemented to replace keytar in the following (merged & published) PRs:

• Zowe CLI (v1 and v2)
  • v1: chore(v1): Update imperative dep. to 4.18.18 to use Secrets SDK #1804
  • v2: feat(pkg): Add secrets SDK and keyring module #1759
• Zowe Explorer (v1 and v2)
  • v1: feat(v1/secrets): Port Secrets SDK changes to v1 zowe-explorer-vscode#2428
  • v2: feat: Use keyring module from @zowe/secrets-for-zowe-sdk to replace use of node-keytar zowe-explorer-vscode#2405
• SCS plugin: chore: use Secrets SDK instead of keytar zowe-cli-scs-plugin#73