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
If I go into the sectigo GUI and try to renew the cert there, it offers me an option regarding whether I would like to renew the cert using the existing key or a new one. I feel this is new functionality but it might just be me being forgetful!
I have tried using the REST API via curl to renew the same certificate as per instructions here:
The above works and I get the new cert ID back as expected. I've also written a custom cert renew function that I'll use in the mean time using python requests (which does the same as the curl in the above document) which also works.
Apologies if this isn't an issue with your library, just thought I'd flag it just in case others are also having the same issue.
Thanks once again,
NS
The text was updated successfully, but these errors were encountered:
Hello,
Firstly thank you for your wonderful library, it's certainly saved me a lot of effort!
I'm hitting an issue on version 2.4.0 (tested with python 3.7 and 3.12) where when I call ssl.renew(id_of_cert) I get the error:
'code': -1002, 'description': 'Cannot parse message body'
If I go into the sectigo GUI and try to renew the cert there, it offers me an option regarding whether I would like to renew the cert using the existing key or a new one. I feel this is new functionality but it might just be me being forgetful!
I have tried using the REST API via curl to renew the same certificate as per instructions here:
https://www.sectigo.com/uploads/audio/Certificate-Manager-20.1-Rest-API.html#resource-SSL-renewById
The above works and I get the new cert ID back as expected. I've also written a custom cert renew function that I'll use in the mean time using python requests (which does the same as the curl in the above document) which also works.
Apologies if this isn't an issue with your library, just thought I'd flag it just in case others are also having the same issue.
Thanks once again,
NS
The text was updated successfully, but these errors were encountered: