Just shipped a new Posh-ACME release, version 3.8.0.
Set-PAOrder now supports modifying some order properties that don’t require generating a new order such as FriendlyName, PfxPass, and the Install switch. If the order has already been completed, changes to FriendlyName and PfxPass will generate new versions of the associated PFX files with the updated values. But changes to the Install switch will only affect future renewals. The GoDaddy plugin will no longer fail on large accounts with more than 100 domains. There’s also a fix for the Cloudflare plugin when used with limited scope tokens.
Set-PAOrdernow supports modifying some order properties such as FriendlyName, PfxPass, and the Install switch that don’t require generating a new ACME order. FriendlyName or PfxPass changes will regenerate the current PFX files with the new value(s) if they exist. Changes to the Install switch will only affect future renewals.
- Fixed FriendlyName, PfxPass, and Install parameters not applying when calling
New-PACertificateagainst an existing order (#178)
- Fixed GoDaddy plugin so it doesn’t fail on large accounts (100+ domains) (#179)
- Updated Cloudflare plugin to workaround API bug with limited scope tokens (#176)
- Fixed DnsSleep and ValidationTimout being null when manually creating an order with
New-PAOrderand finishing it with
- Added parameter help for -NewKey on
New-PAOrderwhich was missing.
- When using
New-PACertificateagainst an already completed order that is not ready for renewal, the informational message has been changed to Warning from Verbose to make it more apparent that nothing was done.
instdev.ps1so it still works when the BouncyCastle DLL is locked and $ErrorActionPreference is set to Stop.
- Updated a bunch of plugin guides with info regarding PowerShell 6.2’s fix for the SecureString serialization bug and enabling the use of secure parameter sets on non-Windows.