Error: WFLYWELD0007 Unable to create a Configuration in AdminUI
search cancel

Error: WFLYWELD0007 Unable to create a Configuration in AdminUI

book

Article ID: 246851

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

 

After applying log4j patch 2.17.0, then the AdminUI doesn't start anymore and it reports errors:

  14:21:05,825 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.iam_siteminder.ear.user_console.war" is using a private module ("org.jboss.as.connector") which may be changed or removed in future versions without notice.
  14:21:06,019 WARN  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0007: Could not load portable extension class org.hibernate.validator.cdi.ValidationExtension: javax.validation.NoProviderFoundException: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.
          at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:291)
          at org.hibernate.validator.cdi.ValidationExtension.<init>(ValidationExtension.java:112)

Environment

 

  AdminUI 12.8SP5 on RedHat 7;
  Policy Server 12.8SP5 on RedHat 7;
  External Admin Store on;

 

Cause

 

There are missing libraries in the library folder:

ls -l command output:

  /opt/CA/siteminder/adminui/standalone/deployments/iam_siteminder.ear/library:
  drwxrwxr-x  2 smuser smuser 4.0K Jul 21 09:22 .
  drwxrwxr-x 14 smuser smuser 4.0K Jul 21 10:42 ..

The following operation hasn't been done:

    Copy only log4j-api-2.15.0.jar and log4j-core-2.15.0.jar in <adminui_installation_path>\standalone\deployments\iam_siteminder.ear\library (1).

Resolution

 

  1. Stop the AdminUI;
  2. Copy log4j-api-2.17.0.jar and log4j-core-2.17.0.jar to the /opt/CA/siteminder/adminui/standalone/deployments/iam_siteminder.ear/library folder;
  3. Start the AdminUI to solve this issue;

Additional Information

 

(1)

    CVE-2021-44228: SiteMinder Resolution to the Log4j Vulnerability