Problem

Issue at restart after an update of TLS accepted versions on standalone.xml. Error « OPVDX001 : erreur de validation dans standalone.xml » with « Invalid value TLS »:

17:01:43,936 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
17:01:44,196 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
17:01:44,205 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
17:01:44,305 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 5.0.0.Final starting
17:01:46,832 ERROR [org.jboss.as.controller] (Controller Boot Thread)

OPVDX001 : erreur de validation dans standalone.xml ----------------------------
|
| 492: </key-managers>
| 493: <server-ssl-contexts>
| 494: <server-ssl-context cipher-suite-filter="TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA" key-manager="serverKeyManager" name="serverSslContext" protocols="TLSv1,TLSv1.1,TLSv1.2" use-cipher-suites-order="true"/>
| ^^^^ Invalid value TLSv1,TLSv1.1,TLSv1.2 for protocols; legal values are
| [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\",
| \"TLSv1.3\"]

Resolution

With last version of Wildfly server embedded with Ebics Gateway 3.4, syntax for setting a list of TLS protocols have changed. List was separated with coma on older version (for instance protocols= “TLSv1,TLSv1.1,TLSv1.2”), with newer version list is separated with space (for instance protocols= “TLSv1 TLSv1.1 TLSv1.2”).