Client Area Sign In

Openprovider Support

Contact our support department using the form on this page. For more information about the availability of our support team, please visit our Knowledge Base. Here, you can also find answers to many questions.




Update for Openprovider API – Getting information about DCV validation

According to the changes made by Comodo for DCV validation methods, we have updated returned values for API method retrieveOrderSslCertRequest.

The structure of the parameter additionalData is the following now:

<additionalData>
  <md5>3eeb773a542f247c99348292612eb545</md5>
  <sha1>bbf760aa34f34dcaeb01a9bc1c8ee729a2cbd6f1198d16a4d6eb6c2e6ca396c6</sha1>
  <sha256>bbf760aa34f34dcaeb01a9bc1c8ee729a2cbd6f1198d16a4d6eb6c2e6ca396c6</sha256>
  <fileLocation>example.com/.well-known/pki-validation/3EEB773A542F247C99348292612EB545.txt</fileLocation>
  <fileContents>bbf760aa34f34dcaeb01a9bc1c8ee729a2cbd6f1198d16a4d6eb6c2e6ca396c6.comodoca.com</fileContents>
  <dnsRecord>_3eeb773a542f247c99348292612eb545.openprovider.com</dnsRecord>
  <dnsValue>bbf760aa34f34dcaeb01a9bc1c8ee729.a2cbd6f1198d16a4d6eb6c2e6ca396c6.comodoca.com</dnsValue>
</additionalData>

There are new fields sha256, fileLocation and fileContents for HTTP(s) validation and dnsrecord and dnsValue for DNS type of validation.

For the cases when you use a previously used CSR for a reissue, renewal or new order, Comodo will add a unique value to the file contents or the DNS record to prevent that the old one is re-used without knowing. An example for a DNS record in such a case:

_c7fbc2039e400c8ef74129ec7db1842c.example.com
  CNAME
c9c863405fe7675a3988b97664ea6baf.442019e4e52fa335f406f7c5f26cf14f.<uniqueValue>.comodoca.com

That is why we highly recommend you to use values returned in the new fields fileContents and dnsValue instead of generating values for DCV validation on your side.

You must be logged in to post a comment.
Menu