Skip to main content

Trendmicro deep security connector

  • Jan 25, 2022 3:07 PM UTC
  • 17 replies
  • 52 views

I have a problem with the trendmicro deep security connector (or maybe a global problem with the lack of configuration of the TLS Root CA file). While testing the connection (with or without TLS enabled) I get the error: "IOError: Could not find a suitable TLS CA certificate bundle, invalid path: False" - I am browsing the documentation, but I can't find anything about it. Please help

17 replies

  • Jan 26, 2022 2:30 PM UTC

File /usr/local/lib/python2.7/site-packages/requests/adapters.py, line 416, in send self.cert_verify(conn, request.url, verify, cert) File /usr/local/lib/python2.7/site-packages/requests/adapters.py, line 228, in cert_verify invalid path: {}.format(cert_loc)) IOError: Could not find a suitable TLS CA certificate bundle, invalid path: False


  • Jan 26, 2022 2:31 PM UTC

So it seems like problem with "requests" configuration


  • Jan 26, 2022 2:31 PM UTC

Huh, the docs are very sparse on the connector. Can you show a screenshot of your current connector config? Just replace all the values with fake data.

To me, it seems like might be a field for cert path and that might not be pointed at the right place


  • Jan 26, 2022 2:32 PM UTC

Sure, just a second (but there is no path to CA file in configuration (hence "False" in path)


  • Jan 26, 2022 2:33 PM UTC

  • Jan 26, 2022 2:33 PM UTC

ahh, ok, I assumed Connector meant there was a connector config as well (which was not in the docs)

hmmm... very strange that it complains about SSL with such a minor config.


  • Jan 26, 2022 2:34 PM UTC

And that error is from running the Ping?


  • Jan 26, 2022 2:34 PM UTC

Have you tried running one of the actions bessides Ping?


  • Jan 26, 2022 2:35 PM UTC

Sometimes the Ping action is not so good


  • Jan 26, 2022 2:35 PM UTC

My immediate suggestion would be to completely remove and delete that integration and then reinstall. It may just be that the Request library did not install correctly


  • Jan 26, 2022 2:36 PM UTC

Yeah, thanx, will try turning it off and on again ;-)


  • Jan 26, 2022 2:36 PM UTC

Nope, nothing changed :(


  • Jan 26, 2022 2:37 PM UTC

and that was with completely removing the integration and re-downloading it?

At this point I'd suggest raising a case with support as there must be a bug in there. Usually there errors you see are from the Requests library not installing correctly


  • Jan 26, 2022 2:38 PM UTC

Hi @Tomasz_PNC_Piłat I faceing with the same issue, did you resolved it?


  • Jan 26, 2022 2:39 PM UTC

I wouldn't call it a solution, but a workaround - I added "return True" at the beginning of cert_verify


  • Jan 26, 2022 2:40 PM UTC

Of course, after the next integration upgrade (if Siemplify programmers do not correct this error), the patching will have to be repeated.


  • Jan 26, 2022 2:42 PM UTC

Great to heard that, @Tomasz_PNC_Piłat can you send a screenshot where exactly did you put this?