Repository navigation
v0.63.0-alpha1
Pre-release0.63.0-alpha1 -- dev build for validation
DEV BUILD. NOT FOR PRODUCTION. This prerelease is built from open pull request #482 so people can validate it before it merges. Cmdlet names, parameters and output can still change before 0.63.0. The supported release is still 0.62.1.
Install
The PowerShell Gallery only offers this build when you ask for prereleases, so a plain Install-Module or Update-Module still gives you 0.62.1.
Install-Module Thycotic.SecretServer -RequiredVersion 0.63.0-alpha1 -AllowPrerelease -Scope CurrentUser
Import-Module Thycotic.SecretServer -RequiredVersion 0.63.0To go back to 0.62.1:
Remove-Module Thycotic.SecretServer -ErrorAction SilentlyContinue
Uninstall-Module Thycotic.SecretServer -RequiredVersion 0.63.0-alpha1 -AllowPrereleaseWithout the Gallery, download Thycotic.SecretServer.zip below, unblock it, extract it to a folder named Thycotic.SecretServer and import the .psd1 from that folder.
What's in it
- 825 new cmdlets for the Secret Server REST API. Exported commands go from 262 to 1,087, and REST coverage goes from 228 to 1,151 of 1,327 verb and route pairs.
- Existing cmdlets only gain parameter sets or parameters. Existing parameters keep their names, positions, Mandatory settings and aliases.
- 14 cmdlets that can break Secret Server or cut off access now print a warning and ask before they send anything.
-Forceskips the question and-WhatIfsends nothing. They cover advanced configuration settings, database configuration, Platform configuration and user mapping, unified mode, and secret key or MEK rotation. - The full list of new cmdlets, changes and fixes is in the 0.63.0 CHANGELOG at this tag.
Breaking Changes
Get-TssSecretPasswordStatus- reads the published route GET v1/secrets/secret-detail/{id}/password-status instead of the internal route internals/secret-detail/{id}/password-status, which is unsupported and can change in any Secret Server release. Parameters and output are unchanged.
Bug Fixes
- Verbose output - the "Command invocation" line printed
-AccessTokenand-OtpCodevalues. Values of-AccessToken,-OtpCode,-ClientSecret,-OnboardingKeyand-PersonalAccessTokennow print asRedacted. Export-TssReport- the export set no longer sendsformat, which Secret Server read as a date format and answered with a 400.Get-TssReportCategory--IdreturnsThycotic.PowerShell.Reports.CategoryDetailinstead of failing on a missing type, and-Allreturns the categories instead of a single null.New-TssSecretDependency- SshKeySecretId, PrivilegedAccountSecretId and ConditionDependencyId of 0 are now sent as null, so a stub fromGet-TssSecretDependencyStubno longer fails with Access denied.Get-TssEventPipeline- output no longer keeps only the last task and trigger, and a pipeline with no filters no longer shows the previous pipeline's filters.Search-TssEventPipeline--PipelinePolicyIdis now sent to Secret Server.Get-TssConfigurationSaml- returns the SAML configuration again when an identity provider exists.
What we need validated
Please run the scripts you already use against 0.62.1 with this build, and tell us about anything that behaves differently. Live testing has not yet covered these areas:
- The 14 guarded cmdlets (warning, prompt,
-Force,-WhatIf),Search-TssDirectoryServiceDomain -SearchTextandStart-TssDirectoryServiceSync -PassThru. These have Pester coverage only. - Upgrade, distributed engines, discovery, launchers, SSH, and Platform admin or migration. These areas have the most live checks still outstanding in the PR's test table.
- Secret Server Cloud and Platform-connected vaults, as well as on-premises.
Report findings as comments on PR #482. Include the Secret Server version, whether it is on-premises or Cloud, the command you ran, and the output with -Verbose.