Advanced Authentication 9.1 SP5 Upgrade - DB schema compatibility

Products

• CA Strong Authentication
• CA Advanced Authentication
• CA Advanced Authentication - Risk Authentication (RiskMinder / RiskFort)

Issue/Introduction

If you are planning the update of Advanced Authentication (AA) 9.1 from SP2 to SP5 and want to understand the backward compatibility between services and schema DB.

If you patch Webfort/Strong Auth server and UDS, and do not execute DB patches, the system fail or continue to work? After that, if you have machines still in SP2, and the DB upgraded to SP5, the SP2 still work?

Environment

Strong Authentication

Risk Authentication

Release: 9.1 SP5 

Resolution

Regarding the update process:

1. Patching WebFort Server and UDS Without Executing DB Patches:

   • If you patch the WebFort server and UDS without executing the corresponding DB patches, the system may not function correctly. The services rely on specific database schema updates to operate properly with the new service pack. Therefore, executing the DB patches is essential to ensure compatibility and avoid potential failures.

2. WebFort server and UDS Running SP2 with an Upgraded DB (SP5):

   • If the database is upgraded to SP5 while WebFort server and UDS are still running SP2, the backward compatibility will work fine. The services running on SP2 should continue to function correctly with the updated database schema. However, it is advisable to upgrade all components, including services and database, to the same service pack level to ensure optimal performance and compatibility.

To summarize, to ensure a seamless update and continued service operation, it is crucial to:

• Execute the DB patches after patching the WebFort server and UDS.
• Upgrade all machines to AA 9.1 SP5 to maintain compatibility with the updated database schema.

If you have any further questions or need assistance during the update process, please feel free to reach out at https://support.broadcom.com.