Symantec Advanced Authentication – Transition from Progress DataDirect Drivers to Native Database Drivers

Products

• CA Strong Authentication

Issue/Introduction

The Symantec Advanced Authentication Product Team is introducing a change in database connectivity beginning with Symantec Advanced Authentication version 9.1.5.3. Refer Product Advisory.

To improve long-term supportability, maintainability, and alignment with vendor best practices, Broadcom is transitioning from Progress DataDirect database drivers to native database drivers for Microsoft SQL Server and Oracle databases.

This article provides information about the transition timeline, customer impact, and recommended validation activities.

Environment

Symantec Advanced Authentication (Strong Authentication and Risk Authentication)

 

Resolution

What Is Changing?

In Symantec Advanced Authentication 9.1.5.3

• Native Microsoft SQL Server and Oracle database drivers will become the default database drivers.
• Existing Progress DataDirect drivers will continue to be included as a temporary fallback option.

In Future Releases

• Support for Progress DataDirect drivers will be removed.
• Only native Oracle and Microsoft SQL Server drivers will be shipped and supported.

Impact to Existing Deployments

Customers currently using Microsoft SQL Server or Oracle databases should review their deployment plans and begin validating the native drivers in lower environments.

No immediate action is required for customers remaining on currently supported releases. However, customers are strongly encouraged to plan for migration to native drivers before upgrading to future releases where DataDirect drivers will no longer be available.

End of Support (EOS) Information

The current Advanced Authentication releases utilizing Progress DataDirect drivers are planned to be announced as End of Support (EOS).

Broadcom intends to provide customers with an extended transition period, with support for legacy DataDirect drivers expected to continue until approximately mid-2028. This timeline is intended to allow customers sufficient time to validate, plan, and complete their migration activities.

Additional EOS announcements and lifecycle information will be communicated separately through standard Broadcom channels.

Recommended Customer Actions

Broadcom strongly recommends that customers perform validation activities in non-production environments before upgrading production systems.

The following validation activities are recommended:

Functional Validation

• Verify user authentication workflows.
• Validate enrollment and registration flows.
• Confirm administrative operations complete successfully.
• Test integrations with external systems and applications.

Performance Validation

• Execute load tests representative of peak production traffic.
• Validate transaction throughput and response times.
• Monitor database connection behavior and resource utilization.

Regression Testing

• Validate all critical authentication use cases.
• Verify reporting, risk analysis, and policy execution functionality.

Additional Information

Frequently Asked Questions

Are DataDirect drivers being removed immediately?

No. Beginning with version 9.1.5.3, DataDirect drivers remain available as a temporary fallback mechanism. They will be removed in a future release.

Will I need to change my database platform?

No. This change affects only the JDBC/database connectivity layer. Existing supported Oracle and Microsoft SQL Server databases remain supported.

Is customer testing required?

While not mandatory, Broadcom strongly recommends functional, regression, and performance testing in lower environments before upgrading production deployments.

What should I do if I encounter issues during validation?

Open a support case with Broadcom Support and provide:

• Product version
• Database type and version
• Relevant application and server logs
• Detailed reproduction steps

For questions regarding this transition or assistance with migration planning, contact Broadcom Support.