Is your feature or enhancement request related to a problem or limitation? Please describe

Currently, Zowe CLI and Explorer for VS Code support using client certificates to authenticate to z/OSMF and the Zowe API ML. This implementation does not (as I understand it) support loading certs from the certificate storage facilities built into the user's operating system.

Describe your enhancement idea

Enhance the Secrets SDK to enable users to specify paths to certificates within the OS certificate store. I am not sure what this means for Linux users, but on MacOS it would require interacting with the keychain, and on Windows this would require interacting with the Windows certificate store.

The end goal would be for Zowe CLI and Zowe Explorer for VS Code users to be able to specify the path and name of the certificate (to retrieve the certificate from the OS cert store) to use for authenticating in their z/OSMF and API ML(nested/base) profiles.

Describe alternatives you've considered

Provide any additional context