From a30caaa664595609012e985d3faf0433843509a7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Richard=20K=C3=B6rber?= <github@shredzone.org>
Date: Fri, 4 Aug 2017 01:06:55 +0200
Subject: [PATCH] Challenge.trigger can be re-invoked

---
 .../main/java/org/shredzone/acme4j/challenge/Challenge.java   | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/acme4j-client/src/main/java/org/shredzone/acme4j/challenge/Challenge.java b/acme4j-client/src/main/java/org/shredzone/acme4j/challenge/Challenge.java
index bf2ff070..c0ad9752 100644
--- a/acme4j-client/src/main/java/org/shredzone/acme4j/challenge/Challenge.java
+++ b/acme4j-client/src/main/java/org/shredzone/acme4j/challenge/Challenge.java
@@ -206,6 +206,10 @@ public class Challenge extends AcmeResource {
     /**
      * Triggers this {@link Challenge}. The ACME server is requested to validate the
      * response. Note that the validation is performed asynchronously by the ACME server.
+     * <p>
+     * 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.
      */
     public void trigger() throws AcmeException {
         LOG.debug("trigger");