- All Implemented Interfaces:
- Direct Known Subclasses:
- See Also:
Method SummaryModifier and TypeMethodDescription
protected booleanChecks if the type is acceptable to this challenge.
getError()Returns a reason why the challenge has failed in the past, if returned by the server.Returns the current status of the challenge.
getType()Returns the challenge type by name (e.g.Returns the validation date, if returned by the server.
protected voidPrepares the response message for triggering the challenge.
protected voidSets the JSON representation of the resource data.
Methods inherited from class org.shredzone.acme4j.AcmeJsonResource
getJSON, invalidate, isValid, update
Methods inherited from class org.shredzone.acme4j.AcmeResource
getLocation, getLogin, getSession, rebind
getTypeReturns the challenge type by name (e.g. "http-01").
getValidatedReturns the validation date, if returned by the server.
getErrorReturns a reason why the challenge has failed in the past, if returned by the server. If there are multiple errors, they can be found in
prepareResponsePrepares the response message for triggering the challenge. Subclasses can add fields to the
JSONBuilderas required by the challenge. Implementations of subclasses should make sure that
prepareResponse(JSONBuilder)of the superclass is invoked.
JSONBuilderto write the response to
acceptableChecks if the type is acceptable to this challenge. This generic class only checks if the type is not blank. Subclasses should instead check if the given type matches expected challenge type.
type- Type to check
setJSONDescription copied from class:
AcmeJsonResourceSets the JSON representation of the resource data.
Challenge. The ACME server is requested to validate the response. Note that the validation is performed asynchronously by the ACME server.
After a challenge is triggered, it changes to
Status.PENDING. As soon as validation takes place, it changes to
Status.PROCESSING. After validation the status changes to
Status.INVALID, depending on the outcome of the validation.
If the challenge requires a resource to be set on your side (e.g. a DNS record or an HTTP file), it must be reachable from public before
trigger()is invoked, and must not be taken down until the challenge has reached
If this method is invoked a second time, the ACME server is requested to retry the validation. This can be useful if the client state has changed, for example after a firewall rule has been updated.