The aveksa.ear file fails to deploy on a WildFly cluster with an access denied error message in RSA Identity Governance & Lifecycle
Originally Published: 2019-06-12
Article Number
Applies To
RSA Platform: WildFly cluster
RSA Version/Condition: 7.1.1
Issue
[Server:bd-1] 05:36:42,961 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 80) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "aveksa.ear")]) - failure description: \{
[Server:bd-1] "WFLYCTL0080: Failed services" => \{"jboss.undertow.deployment.default-server.default-host./aveksa" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./aveksa: java.lang.ExceptionInInitializerError
[Server:bd-1] Caused by: java.lang.ExceptionInInitializerError
[Server:bd-1] Caused by: java.lang.SecurityException: PBOX00016: Access denied: authentication failed"},
[Server:bd-1] "WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.deployment.default-server.default-host./aveksa"],
[Server:bd-1] "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
[Server:bd-1] }
[Server:bd-1] 05:36:42,965 ERROR [org.jboss.as.server] (ServerService Thread Pool – 80) WFLYSRV0021: Deploy of deployment "aveksa.ear" was rolled back with the following failure message:
[Server:bd-1] \{
[Server:bd-1] "WFLYCTL0080: Failed services" => \
Steps used to deploy the ear were:
- Configure the domain node by modifying domain.xml and host.xml.
- Configure and run configureWildfly.sh.
- Deploy the aveksa.ear by running the following commands as user 'oracle':
# /home/oracle/wildfly/bin/jboss-cli.sh -c --controller=<ip address>
[domain@localhost:9990]: deploy /tmp/repackaged_ear_dir/aveksa.ear --server-groups-img-server-groupCause
Resolution
Complete steps to deploy the ear are:
- Configure the domain node by modifying domain.xml and host.xml.
- Reboot the domain node. As the root user run the linux 'shutdown -r [time]' command where [time] is the amount of time before the system shuts down. To shutdown immediately use 'now' as in the following:
shutdown -r now
- Configure and run configureWildfly.sh.
- Deploy the aveksa.ear by running the following commands as user 'oracle':
# /home/oracle/wildfly/bin/jboss-cli.sh -c --controller=<ip address>
[domain@localhost:9990]: deploy /tmp/repackaged_ear_dir/aveksa.ear --server-groups-img-server-group
Related Articles
How to manually deploy an aveksa ear file in RSA Identity Governance & Lifecycle 964Number of Views "Access Denied" error when attempting to view detailed information on the RSA Via Lifecycle and Governance Users page 68Number of Views Access denied error when running sync-tokens command in Authentication Manager 8.x 289Number of Views Error message "Access denied - User not a member of any identity source in access policy" in RSA SecurID Access 80Number of Views Error 2004: Unable to communicate with server Access Denied when running RSA Authentication Manager Bulk Admin (AMBA) script 213Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?