Understand how to create two seperate connections with seperate TNS_ADMIN, sqlnet.ora in same process

[karkan20]

Task:
I am currently testing encrypted and unencrypted Oracle database connections using Node.js with the oracledb package.

Setup:
One connection should use TNS_ADMIN pointing to a sqlnet.ora file configured for an encrypted connection.
Another connection should use TNS_ADMIN pointing to a sqlnet.ora file configured for an unencrypted connection.

Issue:
I encountered an issue where, once the process is set up with either the encrypted or unencrypted connection, changing the TNS_ADMIN path does not seem to apply. Despite modifying the TNS_ADMIN to point to a different path, it appears that the configuration from the first connection setup persists internally.

Could you please assist with this issue or provide insights on how to ensure that the connection configuration is updated correctly when switching between encrypted and unencrypted connections?

Thank you.

[sudarshan12s]

Normally we keep 2 alias in tnsnames.ora which stays in $TNS_ADMIN folder. We use one of the alias based on application logic.

Ex:
tnsnames.ora can have 2 entries

secureService = (description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=adb.us-ashburn-1.oraclecloud.com))(connect_data=(service_name=r23ai_high.adb.oraclecloud.com))(security=(ssl_server_dn_match=yes)))

tcpService      = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=host1)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=svc1.us.oracle.com))) 

Application can pass alias in connectString param in oracledb.getConnection dynamically before creating a connection.

Does this help in your case?

[sudarshan12s]

The changes in sqlnet.ora (inside $TNS_ADMIN) for NNE TCPS connections still need to be present. Within an application, some connections can use TCP while others use TCPS, and combining them should not be an issue.

Sqlnet.encryption_client = required
Sqlnet.encrytion_types_client = aes256
Sqlnet.crypto_checksum = required
Sqlnet.crypto_checksum_types_client =sha512

Please see NNE is only for thick mode. So initOracleClient call needs to be present in application.

[karkan20]

Thanks I was able to make encryption optional in sqlnet.ora by mentioning encryption as ACCEPTED and defined actual REQUIRED implementation in encrypted alias tnsnames.ora. I was able to segregate unencrypted vs encryption connections.