Currently, extension vaults handle user authentication individually, and will prompt the user as needed. But for unattended scripts, there is a common need to unlock SecretManagement extension vaults without user interaction.
For this case there should be a SecretManagement 'Unlock-SecretVault' command that an extension vault can optionally support if needed (some vaults are authenticated by current user log-in and need no additional unlock operation).
The Unlock-SecretVault can initially just take two parameters:
Name: name of vault to unlock
Password: password (as SecureString object) used to unlock the vault
Currently, extension vaults handle user authentication individually, and will prompt the user as needed. But for unattended scripts, there is a common need to unlock SecretManagement extension vaults without user interaction.
For this case there should be a SecretManagement 'Unlock-SecretVault' command that an extension vault can optionally support if needed (some vaults are authenticated by current user log-in and need no additional unlock operation).
The Unlock-SecretVault can initially just take two parameters: Name: name of vault to unlock Password: password (as SecureString object) used to unlock the vault