Errors while limiting WildFly layers

[talcher]

Hello the EJBCA team,

I have successfully installed EJBCA 9.0 using WildFly 32, following your installation guide.

Then, I wanted to limit WildFly layers, as suggested in the Layers Used By EJBCA paragraph.

My first commande to get such a limited WildFly through Galleon was:
install wildfly:current#32.0.1.Final --dir=/tmp/wildfly-32.0.1.Final --default-configs=standalone/standalone.xml --layers=cloud-server,deployment-scanner,ejb-lite,remoting,resource-adapters,undertow,io,jsf,mail,webservices,-jsonb,-jms-activemq,-observability,-jmx-remoting,-messaging-activemq,-core-tools,-management,elytron,-bean-validation
As you can read, I just added -core-tools,-management,elytron,-bean-validation at the end of your suggested command.
When I started WildFly, the process stopped immediately and I got the following error:

2025-02-13 10:14:20,542 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
at org.jboss.as.server@24.0.1.Final//org.jboss.as.server.ServerService.boot(ServerService.java:386)
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:362)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.wildfly.extension.bean-validation
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:84)
at org.jboss.as.server@24.0.1.Final//org.jboss.as.server.parsing.StandaloneXml_18.readServerElement(StandaloneXml_18.java:224)
at org.jboss.as.server@24.0.1.Final//org.jboss.as.server.parsing.StandaloneXml_18.readElement(StandaloneXml_18.java:128)
at org.jboss.as.server@24.0.1.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:115)
at org.jboss.as.server@24.0.1.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:35)
at org.jboss.staxmapper@1.5.0.Final//org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:118)
at org.jboss.staxmapper@1.5.0.Final//org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:72)
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112)
... 3 more
Caused by: java.util.concurrent.ExecutionException: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:79)
... 10 more
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:112)
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:63)
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:60)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: org.jboss.modules.ModuleNotFoundException: org.wildfly.extension.bean-validation
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:301)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:287)
at org.jboss.as.controller@24.0.1.Final//org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:95)
... 9 more

So I gave it another try, but without excluding bean-validation. My new command was therefore:
install wildfly:current#32.0.1.Final --dir=/tmp/wildfly-32.0.1.Final --default-configs=standalone/standalone.xml --layers=cloud-server,deployment-scanner,ejb-lite,remoting,resource-adapters,undertow,io,jsf,mail,webservices,-jsonb,-jms-activemq,-observability,-jmx-remoting,-messaging-activemq,-core-tools,-management,elytron
As you can read, I just added -core-tools,-management,elytron at the end of your suggested command.
On starting, WildFly went a very few steps further, but I soon got errors with my different keystores. One of those errors reads:

2025-02-13 10:20:14,157 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.security.key-store.httpsKS: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.httpsKS: WFLYELY00004: Unable to start the service.
at org.wildfly.extension.elytron@24.0.1.Final//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:187)
at org.jboss.msc@1.5.4.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1617)
at org.jboss.msc@1.5.4.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1580)
at org.jboss.msc@1.5.4.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1438)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.io.IOException: WFLYELY00910: Password cannot be resolved for key-store '/path/to/keystore/keystore.p12'
at org.wildfly.extension.elytron@24.0.1.Final//org.wildfly.extension.elytron.KeyStoreService.resolvePassword(KeyStoreService.java:334)
at org.wildfly.extension.elytron@24.0.1.Final//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:141)
... 8 more

Needless to say that I had previously copied/pasted the content of the /path/to/keystore/ from the default WildFly configuration to this limited one. Here are the files it contains:

• credentials
• my different .p12 files

Could you please tell me what I am doing wrong?

Thanks a lot!

talcher

[primetomas]

"Password cannot be resolved for key-store '/path/to/keystore/keystore.p12" sounds like you don't have a credential store.

[talcher]

Isn't the credential store you are refering to the /path/to/keystore/credentials file?

[primetomas]

it is likely so yes, at least for me. The credentials file need to have an entry matching the alias that you have defined for keystore.p12. For example:

Set by:
/opt/wildfly/bin/jboss-cli.sh --connect '/subsystem=elytron/credential-store=defaultCS:add-alias(alias=httpsKeystorePassword, secret-value="password")'

See: https://docs.keyfactor.com/ejbca/latest/wildfly-35#id-(9.2)WildFly35-ConfigureTLS

[talcher]

Thank you for your answers, Tomas.

Misconfiguration found regarding my second try: my apologies.

What about my first try, i.e. my installing WildFly without bean-validation?
In case it could help: with such a WildFly instance, there is no such file as wildfly/bin/jboss-cli.sh; therefore, I copied-pasted the standalone.xml file from my first successful installation of EJBCA, i.e. the installation with all the recommended WildFly modules.
Let me know if I am getting fuzzy!