Support EAB (External Account Binding) account credentials
bugproof opened this issue · 0 comments
bugproof commented
There is no way to use it with ZeroSSL's ACME server
fail: LettuceEncrypt.Internal.AcmeCertificateLoader[0]
ACME state machine encountered unhandled error
Certes.AcmeRequestException: Fail to load resource from 'https://acme.zerossl.com/v2/DV90/newAccount'.
urn:ietf:params:acme:error:externalAccountRequired: The request must include a value for the "externalAccountBinding" field
at Certes.Acme.IAcmeHttpClientExtensions.Post[T](IAcmeHttpClient client, Uri uri, Object payload, Boolean ensureSuccessStatusCode)
at Certes.Acme.AccountContext.NewAccount(IAcmeContext context, Account body, Boolean ensureSuccessStatusCode)
at Certes.AcmeContext.NewAccount(IList`1 contact, Boolean termsOfServiceAgreed)
at LettuceEncrypt.Internal.AcmeClient.CreateAccountAsync(String emailAddress)
at LettuceEncrypt.Internal.AcmeCertificateFactory.CreateAccount(CancellationToken cancellationToken)
at LettuceEncrypt.Internal.AcmeCertificateFactory.GetOrCreateAccountAsync(CancellationToken cancellationToken)
at LettuceEncrypt.Internal.AcmeStates.BeginCertificateCreationState.MoveNextAsync(CancellationToken cancellationToken)
at LettuceEncrypt.Internal.AcmeCertificateLoader.ExecuteAsync(CancellationToken stoppingToken)
Certes supports this
so it's on LettuceEncrypt end