Error creating certificate from Entrust Certificate Services about win-acme

[WouterTinus]

I have made one small change that solves the crash but I kind of doubt that this leads to a usable solution. Leaving out the finalization step from the order payload means that the server is not compliant to the ACME standard as defined in RFC8555.

That field missing means that no CSR can/will submitted to the service, which means that we don't have access to the certificate's private key (because it's not using the one we've generated).

Presumably that means the key is generated by Entrust (bad for security, that means they have access and can leak it) and sent with the certificate download or something, but that is not how things are supposed to work.

I cannot test this because I'm not going to pay 220 dollars for their yearly subscription just to be able to test/support out their non-standard solution. How these people expect to compete against free is beyond me 😄.

Anyway you can try the build here: https://ci.appveyor.com/project/WouterTinus/win-acme-s8t9q/builds/49746660/artifacts

[danieltintinkarlsson]

Thank you Wouter :) I will try it.

It could perhaps be that we are using OV certificates which means that you cannot input anything you like into the CSR, could that perhaps generate this error? Concidering that if i press retry when i get the error it actually works?

As for the CSR being saved by Entrust, im quite uncertain, i will look into this, thank you! :D

[WouterTinus]

Did you manage to try build 1667?

[danieltintinkarlsson]

It works like a charm! Thank you very much Wouter! :)

[WouterTinus]

This has been released in 2.2.9