Skip to content
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

Upgrade API calls to InCommon to use REST API #43

Open
5 tasks
chmc3 opened this issue Sep 27, 2023 · 0 comments
Open
5 tasks

Upgrade API calls to InCommon to use REST API #43

chmc3 opened this issue Sep 27, 2023 · 0 comments
Assignees

Comments

@chmc3
Copy link

chmc3 commented Sep 27, 2023

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.

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants