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
{{ message }}
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.
We need a challenge type to cover types of validation that can't be done automatically, in band to ACME. For example, a CA doing OV or EV validation might need the applicant to upload some documents through a web form. We should add a generic "out-of-band" challenge type that has a URL for a web site where the applicant gan go for instructions. I think the challenge object would look something like:
There would be no response object; you just click the link, and when you complete the instructions there, the CA reflects this in the "status" field of the challenge object.
The text was updated successfully, but these errors were encountered:
A few months back I wrote up a proposal for this idea -- the hope is that ACME could evolve to become the language that all cert issuers talk to support a standard for cert management and exchange.
We need a challenge type to cover types of validation that can't be done automatically, in band to ACME. For example, a CA doing OV or EV validation might need the applicant to upload some documents through a web form. We should add a generic "out-of-band" challenge type that has a URL for a web site where the applicant gan go for instructions. I think the challenge object would look something like:
There would be no response object; you just click the link, and when you complete the instructions there, the CA reflects this in the "status" field of the challenge object.
The text was updated successfully, but these errors were encountered: