Currently, the Cert Services tool utilizes the Comodo SOAP API to request, renew, and fetch certificates. The current API is questionable in support, and has previously experienced outages with lackluster resolution as Sectigo will often claim that they no longer have a Comodo API.
As a result, we would like to move to using the REST API in our calls to Sectigo. This may be a significant effort as the logic used currently with the SOAP calls do not always translate to the REST API. So this issue will not be a one step effort.
[x] Review current use of SOAP API in Cert Services
[ ] Review REST API documentation
[ ] Outline where the REST calls can be used as a replacement vs where they will need to have logic reworked
[ ] Test REST API calls to confirm ability to call Sectigo and write to Cert Services DB
[ ] Design process to respond to API call failures, including notification to user and IAM team
Currently, the Cert Services tool utilizes the Comodo SOAP API to request, renew, and fetch certificates. The current API is questionable in support, and has previously experienced outages with lackluster resolution as Sectigo will often claim that they no longer have a Comodo API. As a result, we would like to move to using the REST API in our calls to Sectigo. This may be a significant effort as the logic used currently with the SOAP calls do not always translate to the REST API. So this issue will not be a one step effort.