SecretManagement preview 6 and SecretStore preview 4
Two updated preview releases are now available on the PowerShell Gallery:
For more information on these modules check out these previous blog posts:
- SecretManagement preview 3/SecretStore preview 1
- SecretManagement preview 4/SecretStore preview 2
- SecretManagement preview 5/SecretStore preview 3
Before installing these modules, please uninstall the current preview versions of the modules and restart your PowerShell session.
To install these updates run the following commands:
Uninstall-Module Microsoft.PowerShell.SecretManagement -Force Uninstall-Module Microsoft.PowerShell.SecretStore -Force # Restart your PowerShell session Install-Module -Name Microsoft.PowerShell.SecretManagement -AllowPrerelease -Repository PSGallery Install-Module -Name Microsoft.PowerShell.SecretStore -AllowPrerelease -Repository PSGallery Register-SecretVault -Name SecretStore -ModuleName Microsoft.PowerShell.SecretStore -DefaultVault -AllowClobber
SecretManagement preview 6 updates
This update to SecretManagement improves the compatibility of the module with Windows PowerShell, and improved the usability of the module by providing more ways to unregister vaults and by setting the first registered vault as default as well a few other changes. Read the full list of changes below:
- Improved compatibility with Windows PowerShell 5.1 (Issue #73)
- The first extension vault added will automatically be designated the default vault (Issue #61)
-Nameproperty now supports string type and wild cards (Issue #57, #58)
-VaultParametershashtable for reserved
Verboseentry and throws error if found
Set-DefaultVaultnow has a
-ClearDefaultparameter that designates no registered vault as the default vault
Register-SecretVaultnow supports a
-Descriptionparameter and registration information will include an optional extension vault description (Issue #46)
SecretStore preview 4 updates
This update to SecretStore focuses on updates which improve the compatibility with Windows PowerShell. Read the full list of changes below:
- Improved compatibility with Windows PowerShell when creating new store files (Issue #28)
- SecretStore binary is now built against net461 to provide full compatibility when run in PowerShell 6 or Windows PowerShell
System.IO.FileSystem.AccessControl.dllis now shipped with module to maintain compatibility with Windows PowerShell
Finding other available extension Vaults
To find other SecretManagement extension vault modules, search the PowerShell Gallery for the “SecretManagement” tag. Some community vault extensions that are available:
Thank you to everyone who has created vaults thus far!
Feedback and support
Community feedback has been essential to the iterative development of these modules. Thank you to everyone who has contributed issues, and feedback thus far! As we approach General Availability, targeted for later this year, for these modules now is the time to test the modules against your scenarios to request changes (especially breaking ones) and discover bugs. To file issues or get support for the SecretManagement interface or vault development experience please use the SecretManagement repository. For issues which pertain specifically to the SecretStore and its cmdlet interface please use the SecretStore repository.
Is there a module to use Azure Key Vault as a store?
There was via the Az.KeyVault module, but it looks like that needs to be updated to support the changes from Preview 3 of SecretManagement.
Will GA module updates clobber our vaults?
Hi! Good tool! However, I am looking for any/all explicit examples:
1. CyberArk integration
2. Saviynt SaaS
3. Saviynt on-prem
4. SafeNet KeySecure