Should the wallet always be created in the client server? Or can we create the wallet in one server and then copy the wallet to an another server and try establish the connectivity?
@@drdb2sqlora when I set up oneway it was working for me and enabling encrypted communication and not authentication. how do I make sure my TLS encrypted process working as expected?
@@alpesh13 Follow the vendor supported way to setup TLS, for Oracle, it is Oracle wallet. If your connection is using the Oracle wallet aka certificates, then it is encrypted TLS/SSL coonection.
@@drdb2sqloraI think he is talking about setting SSL_CLIENT_AUTHENTICATION=false in server's sqlnet.ora file. I guess this setting will ensure that while the server sends it's certificates to client for validation but doesn't expect the client to authenticate or verify itself. I came across this situation while setting up the TCPS communication for an oracle server myself, but didn't try it as I was working under a deadline to enable 2-way SSL communication.
I have the same error. I‘m using Oracle Database 21c XE on a Oracle Linux Server. My Instant Client is on an OpenSUSE machine. Did you find a solution. If so please tell me the solution. I‘m getting desperate.
