[jboss-jira] [JBoss JIRA] (WFCORE-4022) The key-store obtain-certificate operation currently fails with "Parameter 'type' may not be null"

[Farah Juma (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Farah Juma updated WFCORE-4022:
-------------------------------
    Description: 
Currently, executing the {{key-store}} {{obtain-certificate}} operation results in:

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

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. 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.

  was:

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

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

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. 



> The key-store obtain-certificate operation currently fails with "Parameter 'type' may not be null"
> --------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-4022
>                 URL: https://issues.jboss.org/browse/WFCORE-4022
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Security
>            Reporter: Farah Juma
>            Assignee: Farah Juma
>
> Currently, executing the {{key-store}} {{obtain-certificate}} operation results in:
> {code}
> {
>     "outcome" => "failed",
>     "result" => undefined,
>     "failure-description" => "Parameter 'type' may not be null",
>     "response-headers" => {"process-state" => "reload-required"},
>     "rolled-back" => true
> }
> {code}
> 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. 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.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)