Microsoft.PowerShell.SecretManagement module doesn't work in a remote session.

[PaulHigin]

Summary of the new feature/enhancement

Currently the module does not work in a remote session because the session user log on does not have the needed security token for Windows CredMan to work, and the BuiltInLocalVault (based on CredMan) is required for registering extension vaults. This is by design for security reasons. The BuildInLocalVault is used to securely store extension vault optional parameters, some of which are assume to contain secrets.

We could consider optionally allowing non secure registration of extension vaults where all information is stored in file. But I am concerned that this might be too limiting for an extension vault, or tempt people into non securely register and use vaults.

Proposed technical implementation details (optional)