Application and Authentication Compatibility

Because ezTLS operates entirely below the application layer, adopting it requires zero changes to your application code or user workflows.

Your applications will continue to use their existing connection methods, connection identifiers, and service names. Furthermore, database user authentication remains completely independent of network encryption—users and applications will continue logging into the database exactly as they do today.

The only changes required to transition from unprotected connections (or legacy NNE) to TLS-based protection are at the network configuration level:

• For TCP connections: Add EZTLS to your accepted encryption-algorithm lists and configure the encryption policy for your target endpoints.
• For TCPS connections: Set EZTLS = ON for the intended scope and ensure clients are using the correct TCPS connection entry.

Note: As with any network change, always verify that your specific combination of clients, servers, and authentication methods supports ezTLS before deploying these configuration changes to production.