-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Missing Authentication Token" errors when using SSL.com's ACME server #372
Comments
It looks like they might be working on the problem. Requests against account endpoints are still throwing errors, but some are now ACME formatted errors like:
The |
@rmbolger Any update on this issue? Did you contact SSL.com in the end and did you get any feedback? |
Not yet. I did open a support request, but unfortunately never got a response and kind of let it languish since then. I've got a test branch, sslcom-compat, that works around the issue by removing all account refresh calls that happen as part of the basic cert request workflow. It works in my local testing, but it's not an ideal solution or something I'm ready to incorporate into an official version yet. Ironically, DigiCert also seems to have a similar issue with their non-free ACME implementation that was reported in issue #394. Make me wonder whether they're both using the same underlying ACME server. I don't currently have any other issues I'm actively working on. So I will try to reach out to ssl.com support again and see if I can get some traction. Since I'm not a paying customer, they don't have a lot of incentive to listen to me though. |
I got at least an initial response to my ticket this time saying
|
No updates from support since this last message and the account endpoints still appears to be throwing the same error from September. |
I own a few certificates from them. I can try to raise an issue as well. Will report here if I'll get any feedback. |
I added a workaround in 4.14.0. If you have already configured a server, you'll need to use |
The ACME server implementation that SSL.com is currently using appears to have some bugs that are preventing Posh-ACME from doing standard tasks like checking account status or updating account contact details.
I started a thread with other client devs on the LE community forums to compare findings. But for now SSL.com is incompatible with Posh-ACME.
The text was updated successfully, but these errors were encountered: