Tenable connector connection failing

[Scorpion81]

Hello,  We are using Tenable Module of Vulnerability Response in our SNOW instance.  There is an APP called tenable connector that needs to be setup as a pre-requsite.  We have a MID-server as well.

The MID-server is unable to connect to the Tenable Security Center host even though we have allowed Port 443 and the username/pwd are configured correctly.  How can i further troubleshoot what is causing the connection to fail ?

[Chris McDevitt]

Scorpion81,

On page 4 step 5 of the "Tenable for VR - Application installation and Configuration Guide V3" did you generate the Access Key and Secret Key?

Next, from the MID Server, I would Open a Web Browser (or use Curl) and connect to the URL to make sure you can connect. 

Some times I will also reconstruct the API call (System Web Services > Outbound > REST Message and look for the Tenable messages), and use it in Postman or Curl for troubleshooting. 

Then the ServeNow Logs, then the MID Server Logs.

Go ahead and mark this as helpful or Correct!

[Weston Wilson]

I was recently having issues setting up the connector using API username and API password with Tenable.sc. Setting the account up as a normal user in Tenable resolved our issue. I would move on to the ECC Queue to look at the specific error if you aren't seeing that in the connector app. 

[Scorpion81]

Hello @Weston Wilson @Chris McDevitt ,

We tried both regular user /pass and API key combo to connect to Tenable.SC but its failing. Here is a screenshot of the error in Connector logs. 

 The tenable.SC documentation says to use regular username/password  but we still went ahead and even enable API keys for our user to see if that works.

[Smashley]

I'm seeing the exact same thing.  We are able to log into Tenable from the MID Server directly.  I have deleted and re-created the connector, and still seeing the same errors as @Scorpion81 .