Skip to main content

Trendmicro deep security connector

  • January 25, 2022
  • 17 replies
  • 41 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

  • January 26, 2022

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


  • January 26, 2022

So it seems like problem with "requests" configuration


  • January 26, 2022

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


  • January 26, 2022

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


  • January 26, 2022

  • January 26, 2022

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.


  • January 26, 2022

And that error is from running the Ping?


  • January 26, 2022

Have you tried running one of the actions bessides Ping?


  • January 26, 2022

Sometimes the Ping action is not so good


  • January 26, 2022

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


  • January 26, 2022

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


  • January 26, 2022

Nope, nothing changed :(


  • January 26, 2022

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


  • January 26, 2022

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


  • January 26, 2022

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


  • January 26, 2022

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


  • January 26, 2022

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