-
Notifications
You must be signed in to change notification settings - Fork 147
ACME Respond Challenge REST API
Endi S. Dewata edited this page Apr 29, 2025
·
3 revisions
This operation submits a response to an ACME challenge as defined in RFC 8555 Section 7.5.1.
To prove control of the identifier and receive authorization, the client needs to provision the required challenge response based on the challenge type and indicate to the server that it is ready for the challenge validation to be attempted.
The client indicates to the server that it is ready for the challenge validation by sending an empty JSON body ("{}") carried in a POST request to the challenge URL (not the authorization URL).
POST /acme/chall/prV_B7yEyA4 HTTP/1.1 Host: example.com Content-Type: application/jose+json { "protected": base64url({ "alg": "ES256", "kid": "https://example.com/acme/acct/evOfKhNU60wg", "nonce": "Q_s3MWoqT05TrdkM2MTDcw", "url": "https://example.com/acme/chall/prV_B7yEyA4" }), "payload": base64url({}), "signature": "9cbg5JO1Gf5YLjjz...SpkUfcdPai9uVYYQ" }
Tip
|
To find a page in the Wiki, enter the keywords in search field, press Enter, then click Wikis. |