If application is 3-tier, then Oracle DB knows only about middle tier & NOTHING about end client directly. Oracle database does not know (& really dos not care) which protocol (OCI, JDBC, etc.) is used by any client. Fiddler doesn't need to sniff or decrypt those manually entered composer requests, because it was the process that generated the requests and will receive the responses directly. For when JDBC is used, sqlnet.ora file is NOT used. I should have to enabled "Decrypt HTTPS traffic" in order to allow composer to use a different protocol that is obviously supported by Fiddler. So I have to go in and turn the "Decrypt HTTPS traffic" setting off in order for the rest of my computer to work, then turn it back on again when I need to test an API directly that only supports TLS 1.2. Set TLS version by editing sslprotocols TLSv1.2 For TLS version 1.3 by add sslprotocols TLSv1.3 We can combine and only allow TLS 1.2 and 1.3 in Nginx by setting: sslprotocols TLSv1.2 TLSv1. Edit nf file or virtual domain config file. ![]() So I can't manually create API requests and test them at the same time as I'm actually testing live webservers that implement the API. Login to Nginx server using the ssh command. BUT, while that setting is on, nothing else on my computer works, as the majority of sites will attempt to use TLS 1.2, but not work because I refused to trust the new root certificate. Do to security policies, I am unable (and frankly unwilling) to do that.Īfter I click that box, now I can use the composer to manually create API requests to servers that only support TLS 1.2. When I turn on "Decrypt HTTPS traffic" to enable that Protocols settings, I get prompted to install a new trusted root certificate.
0 Comments
Leave a Reply. |