- Fix for type initialization error on WindowsPowerShell (Issue #).
- Fix for Windows platform UserName character casing bug (Issue #62).
- Workaround Windows bug where UserName environment variable is incorrect case (Issue #62).
-
Fix race condition where updating store configuration fails with invalid password (Issue #79).
-
Update password failure errors are now surfaced to users (Issue #79).
-
Fix for random data corruption when password is updated.
-
Metadata does not accept datetime from Get-Date (Issue #59).
-
Add better error message when running under Windows built-in accounts (Issue #63).
-
Store update no longer removes current information on read failure.
- Add support for SecretManagement
Unlock-SecretVaultcommand.
-
Set-SecretStoreConfigurationwill throw an error when setting a password if a password has already been set. In this caseSet-SecretStorePasswordmust be used to reset an existing password. -
Fixed license Url in module manifest.
- Minor changes to architecture document.
- Minor changes to help file format.
- The
-Forceparameter was removed from theSet-SecretStoreConfigurationcommand, and instead the-Confirm:$falseshould be used to suppress PowerShell prompting in automation scripts.
Set-SecretStoreConfigurationcommand now takes a-Passwordparameter so that there is no need to prompt for a password (Issue #46).
-
Set-Secretvault command now supports optionalMetadataparameter (Issue #46). -
Add optional
Set-SecretInfovault command that setsMetadatato an existing vault secret (Issue #46).
- Add support for SecretManagement secret metadata (Issue #46).
- Take SecretStore module to version 0.9.0 release candidate.
- Windows PowerShell incompatibility when creating new store files (Issue #28).
-
SecretStore binary is now built against net461 to provide full compatibility when run in PowerShell 6+ or WindowsPowerShell.
-
System.IO.FileSystem.AccessControl.dllis now shipped with module to maintain compatibility with WindowsPowerShell.
-
Set-SecretStoreConfigurationnow has a-PassThruparameter to write the store configuration object to the pipeline, and no longer writes the configuration object by default (Issue #25). -
A
-PasswordTimeoutvalue of zero now allows the provided password to be used only once (Issue #30). -
When setting a password, an empty password is no longer accepted (Issue #31).
-
Set-SecretStorePasswordnow has a parameter set that takes old/new password arguments, to allow setting password by automation (Issue #26). -
Reset-SecretStorenow has a new-Passwordand-PassThruparameter. -
Reset-SecretStorewill now prompt immediately for a new password, if password authentication is selected and prompt interaction is allowed (Issue #34).
This version of SecretStore is incompatible with previous versions because the configuration format has changed.
The previous file store cannot be read by the new version and you will need to reset the store Reset-SecretStore after installing the new version.
!!! Be sure and save your current stored secrets so they can be re-added !!!
-
Set-SecretStoreConfigurationnow supports-Authenticationand-Interactionparameters instead of-PasswordRequiredand-DoNotPrompt. -
Rename
Update-SecretStorePasswordtoSet-SecretStorePassword. -
Remove
Unlock-SecretStoreplain text parameter set.
Set-SecretStoreConfigurationnow throws an error if called with no parameters.
-
Add ProjectUri to manifest file.
-
Reset-SecretStorenow defaults to 'No' when prompting to continue.