-
Bug
-
Resolution: Done
-
Blocker
-
EAP-XP-4.0.0.CR1
-
None
XP4 doesn't contain module `org.wildfly.extension.elytron-oidc-client` and default microprofile configuration blocking start of EAP.
Is not possible add `org.wildfly.extension.elytron-oidc-client` extension to EAP over CLI interface. This cause following failure.
[standalone@localhost:9990 /] /extension=org.wildfly.extension.elytron-oidc-client:add
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0310: Extension module org.wildfly.extension.elytron-oidc-client not found",
"rolled-back" => true
}
In case of manual add to standalone.xml or microprofile configuration it cause error during start and EAP does not start.
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@15.0.6.Final-redhat-20220106//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server@15.0.6.Final-redhat-20220106//org.jboss.as.server.ServerService.boot(ServerService.java:403)
at org.jboss.as.controller@15.0.6.Final-redhat-20220106//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.wildfly.extension.elytron-oidc-client