-
Notifications
You must be signed in to change notification settings - Fork 38
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
Issue with acme_ca_handler.py and Sectigo #122
Comments
Hi, Thank you for providing the logs. Sectigo is using a non-standardized challenge-type /GrindSa |
Hi @grindsa, Best, |
Hi, I pushed some fixes into a separate branch which should hopefully address your issue. The changes are in the acme_ca_handler.py only; it should be enough to replace this file on your system. Please test and let me know if it works for you. /G. |
Hi @grindsa, Best, |
Thank you for your confirmation. Changes got merged into devel and will be release in the upcoming days. Closing the issue.... |
Hi all,
thanks a lot for providing
acme_ca_handler.py
. I tried to use it with Sectigo in the context of Trusted Certificate Service where Sectigo provides certicates for EU's NRENs (national research and education networks).It works fine using certbot (see logs at the end of this issue):
certbot certonly --manual --preferred-challenges dns -d 'some.allowed.domain' \ --agree-tos --email some@valid.email --server https://acme.sectigo.com/v2/OV \ --eab-kid XXXXXXXXXXX --eab-hmac-key YYYYYYYYYYYYY
Basically, I get a valid certificate without the need to complete any challenge (i.e., as I'm a trusted admin, I can issue certificates).
But issuing a certificate fails using
acme_ca_handler.py
as ca_handler. I tried debugging it and it seems that Sectigo is using some proprietary challengesectigo-email-01
(without any actions to perform):which results in the following message:
Any ideas how to fix this?
Best,
Dennis
The full log of acme_ca_handler is as follows:
This is the output of
certbot
with-vvvvv --debug
flags:The text was updated successfully, but these errors were encountered: