Guidance for Migrating Host Infrastructure from JBoss EAP 7.x to 8.x in CA Advanced Authentication Environments

Products

• CA Risk Authentication

Issue/Introduction

• Current State: Addressing vulnerabilities in JBoss 7.x by evaluating migration to JBoss 8.

• Reference Doc: Red Hat JBoss 7.x to 8 Migration Guide

• Target Application: Web application acting as an authentication broker, communicating via SOAP calls with CA Advanced Authentication.

Question:

Will migrating this broker application to JBoss 8 result in any functional or compatibility impact?

Environment

CA Advanced Authentication

Cause

This article provides guidance applies both to host servers running CA Advanced Authentication components and to intermediate broker applications interacting with AA via web services (SOAP/REST).

Resolution

Core Architecture Impact Matrix

Component Area	Upgrading Host Server to JBoss 8.x	Impact on External Broker/Client Applications
SOAP/WSDL Interface	No Impact. XML schemas, SOAP contracts, and API operational behavior remain identical.	None. External applications interacting via HTTP/SOAP do not require payload or contract rewrites.
Java Runtime (JVM)	High Impact. JBoss 8.x deprecates Java 8 and requires Java 17 or Java 21.	Medium. External clients must ensure their TLS negotiation supports the tighter cipher suites enforced by Java 17+.
API Namespaces	High Impact. JBoss 8.x adopts Jakarta EE 10 (jakarta.* namespace replacement of legacy javax.*).	Low to High. Applies only if the broker application itself is being redeployed onto JBoss 8.x.
Security Framework	High Impact. Legacy PicketBox security domains are fully removed; WildFly Elytron is required.	Low. Configuration changes are isolated to JBoss standalone.xml / domain settings.

Migration Checklist & Verification Steps

1. Verify Deployment Media:

   Ensure you obtain the dedicated JBoss 8.x deployment patch/archive (i.e., Symantec-AdvancedAuthentication-Patch-9.1.5.2--JBOSS-8x.zip or higher) from the Broadcom Support Portal.

   

2. JVM Prerequisites:

   Install and configure OpenJDK 17 or OpenJDK 21 on the host environment prior to initializing JBoss EAP 8. Refer AdvancedAuthentication platform-support-matrix

3. Configuration Conversion:

   Migrate custom datasources, JMS queues, and SSL settings from JBoss 7.x standalone.xml into the new JBoss 8 configuration structure using Elytron syntax.

4. End-to-End Testing (UAT):

   Execute functional authentication and risk evaluation flows from client applications through broker services to CA AA to validate network connectivity and SSL negotiation.