Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4022

The key-store obtain-certificate operation currently fails with "Parameter 'type' may not be null"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 6.0.0.CR1
    • None
    • Security
    • None

      Currently, executing the key-store obtain-certificate operation results in:

      {
    "outcome" => "failed",
    "result" => undefined,
    "failure-description" => "Parameter 'type' may not be null",
    "response-headers" => {"process-state" => "reload-required"},
    "rolled-back" => true
}

      This is due to a recent Let's Encrypt change where a new challenge type was introduced but not officially added to the ACME v2 protocol spec yet. The WildFlyAcmeClient only needs to be able to handle the "http-01" challenge type but should be able to handle being presented with many challenge options.

              fjuma1@redhat.com Farah Juma
              fjuma1@redhat.com Farah Juma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: