replay-nonce response header from POST /acme/{provisioner-name}/order/{order-id}/finalize
Verifies that the previous challenge has been completed.
location header from http response you got from newOrderResponse
replay-nonce response header from POST /acme/{provisioner-name}/challenge/{challenge-id}
Parses the response from POST /acme/{provisioner-name}/order/{order-id}.
HTTP response body
finalize url to use with finalizeRequest
Generates a new client Dpop JWT token. It demonstrates proof of possession of the nonces (from wire-server & acme server) and will be verified by the acme server when verifying the challenge (in order to deliver a certificate).
Then send it to POST /clients/{id}/access-token
https://staging-nginz-https.zinfra.io/api/swagger-ui/#/default/post_clients__cid__access_token on wire-server.
of the client Dpop JWT. This should be equal to the grace period set in Team Management
you get by calling GET /clients/token/nonce on wire-server as defined here https://staging-nginz-https.zinfra.io/api/swagger-ui/#/default/get_clients__client__nonce
Parses the response from GET /acme/{provisioner-name}/directory.
Use this AcmeDirectory in the next step to fetch the first nonce from the acme server. Use
AcmeDirectory.newNonce.
HTTP response body
Final step before fetching the certificate.
replay-nonce response header from POST /acme/{provisioner-name}/order/{order-id}
Parses the response from POST /acme/{provisioner-name}/order/{order-id}/finalize.
HTTP response body
the certificate url to use with certificateRequest
Should only be used internally
For creating a new acme account. This returns a signed JWS-alike request body to send to
POST /acme/{provisioner-name}/new-account.
you got from calling HEAD {@link AcmeDirectory.newNonce}
Parses the response from POST /acme/{provisioner-name}/new-account.
HTTP response body
Creates a new authorization request.
one of the URL in new order's authorizations from newOrderResponse)
replay-nonce response header from POST /acme/{provisioner-name}/new-order (or from the
previous to this method if you are creating the second authorization)
Parses the response from POST /acme/{provisioner-name}/authz/{authz-id}
HTTP response body
Creates a new challenge request for Wire Dpop challenge.
returned by wire-server from https://staging-nginz-https.zinfra.io/api/swagger-ui/#/default/post_clients__cid__access_token
replay-nonce response header from POST /acme/{provisioner-name}/authz/{authz-id}
Parses the response from POST /acme/{provisioner-name}/challenge/{challenge-id} for the DPoP challenge.
HTTP response body
Creates a new challenge request for Wire Oidc challenge.
you get back from Identity Provider
replay-nonce response header from POST /acme/{provisioner-name}/authz/{authz-id}
Parses the response from POST /acme/{provisioner-name}/challenge/{challenge-id} for the OIDC challenge.
HTTP response body
Creates a new acme order for the handle (userId + display name) and the clientId.
replay-nonce response header from POST /acme/{provisioner-name}/new-account
Parses the response from POST /acme/{provisioner-name}/new-order.
HTTP response body
Creates a request for finally fetching the x509 certificate.