https://community.splunk.com/t5/Getting-Data-In/REST-API-rest-ta-SSL-Error-20-Not-a-Directory/m-p/429356#M75218 <P>I am using the rest_ta app (<A href="https://splunkbase.splunk.com/app/1546/">https://splunkbase.splunk.com/app/1546/</A>).</P> <P>However, I have realized this application, by default, has SSL verify set to false.</P> <P>I was creating a custom response handler for this app and kept receiving an SSL error 20 Not a Directory when my custom handler used the requests.get call and I did not set verify=False. Since I don't want to write code that leaves me open to a MITM attack, can anyone provide a solution? Or at least an explanation?</P> <P>FYI: The error occurs no matter what HTTPS endpoint is called so its not an issue of the endpoint using a self signed certificate. Also, there is no "Enterprise MITM" proxy as I have confirmed the certificate chain using OpenSSL.</P> Tue, 06 Aug 2019 18:53:25 GMT scoughlin1 2019-08-06T18:53:25Z https://community.splunk.com/t5/Getting-Data-In/REST-API-rest-ta-SSL-Error-20-Not-a-Directory/m-p/429356#M75218 <P>I am using the rest_ta app (<A href="https://splunkbase.splunk.com/app/1546/">https://splunkbase.splunk.com/app/1546/</A>).</P> <P>However, I have realized this application, by default, has SSL verify set to false.</P> <P>I was creating a custom response handler for this app and kept receiving an SSL error 20 Not a Directory when my custom handler used the requests.get call and I did not set verify=False. Since I don't want to write code that leaves me open to a MITM attack, can anyone provide a solution? Or at least an explanation?</P> <P>FYI: The error occurs no matter what HTTPS endpoint is called so its not an issue of the endpoint using a self signed certificate. Also, there is no "Enterprise MITM" proxy as I have confirmed the certificate chain using OpenSSL.</P> Tue, 06 Aug 2019 18:53:25 GMT https://community.splunk.com/t5/Getting-Data-In/REST-API-rest-ta-SSL-Error-20-Not-a-Directory/m-p/429356#M75218 scoughlin1 2019-08-06T18:53:25Z