You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Posh-ACME now fully supports the new dns-persist-01 challenge type based on draft-ietf-acme-dns-persist-02. The module still works with draft 01 based ACME servers, but the _validation-persist records must already exist or you must use the Advanced parameter set from Publish-DnsPersistChallenge to publish draft 01 compatible records. There are no available draft 02 ACME CAs to test against yet, so testing has been largely theoretical and bugs may surface once there is something real to test against.
Breaking Change:-UseAllDomains has been removed from (Un)Publish-DnsPersistChallenge and they no longer attempt to skip records that would be covered by another wildcard record.
Breaking Change: The FromOrder parameter set on (Un)Publish-DnsPersistChallenge should still work the same way, but it will now only work against draft 02+ compatible ACME servers.
Breaking Change: Wildcard FQDNs passed to (Un)Publish-DnsPersistChallenge will now automatically have policy=wildcard added to that specific record without needing to pass the -AllowWildcard switch. Using the switch still adds it to all records being processed.
Breaking Change: The Standalone parameter set on (Un)Publish-DnsPersistChallenge has been replaced by 3 new parameter sets. See the function docs and persist guide for details.
3 new parameter sets for (Un)Publish-DnsPersistChallenge that allow for more pre-provisioning use cases, some of which don't require publishing from the same system you request the certs from. See the function docs and persist guide for details.
New Get-DnsPersistAccountUri function which calculates the hashed accountUri field required in draft 02 compatible persistent records.
New Get-PublishedPersistChallenge function which returns the details of persistent records published from the current Posh-ACME config. The objects returned by this function can be piped to (Un)Publish-DnsPersistChallenge.
Get-PAAccount now returns two additional fields
pubkey which is a public-only version of the existing ACME account key value
thumbprint which is the JWK thumbprint value of the ACME account key
The default display output for a PAAccount object now includes the thumbprint by default
dns-persist-01 has been added to the allowed values for -DnsVariant on New-PACertificate, New-PAOrder, and Set-PAOrder.
The -DnsVariant parameter on the older (Un)Publish-Challenge functions only allows dns-01 and dns-account-01.
No user-facing changes to Submit-ChallengeValidation, but lots of refactoring internally to support the various dns-persist-01 workflows.
New "shared" PluginArgs parameter, PublishPersist, which must be $true if you want a dns-persist-01 enabled order to automatically attempt to re-publish the necessary persistent records on each renewal. This shouldn't be necessary when using pre-provisioning.