Can't Discover Linux Server because it doesn't find credentials...Even though I provided them

[Fares1]

Hi!

My problem is in the title of the topic, I've provided SSH Credentials to my Kingston ServiceNow instance and I've validated them by testing them, but whenever I try to discover the linux server, Discovery logs tell me that they couldn't find any credentials associated with them (even though, as I said, I've provided them) and can't finish classifying the CI.

I have already successfully discovered this CI with my other London instance, without any issues and I didn't need to provide extra information in that instance.

Any suggestions to what to do next?

Thanks in advance,

Fares

[Community Alums]

try adding this parameter to your midservers

mid.ssh.use_snc       and set it to true

I have seen this issue with versions of ssh.

[Vini]

Hi Fares,

We also got the same error then identified that MiD Server "Supported Application" has "Discovery" and "SSH" capability should assign and make sure that "IP Ranges" on the mid Server should cover target IP.

Also, add "mid.ssh.use_snc" = "true" Property to Configuration Parameter” on the MiD Server.

I hope you should resolve your issue with these steps.

Thanks & Regards,

Vinil.

[tim_broberg · Accepted solution]

Richard hits a lot of great points.

A few other things to look at that may help you debug:

1. The ecc_queue input for SSHCommand's that fail to authenticate will have a credential debug section that indicates what credentials were tried and such.
2. One difference between credential test and SSHCommand is that Credential Test tries only one credential. Sometimes, the ssh server loses patience when we try a large number of credentials.
3. If all else fails, once you switch to sncssh, you can add a debug = true parameter to your probe (or enable ssh debug for the mid) and see everything that's going on with the ssh connection. It's a lot of information to filter through, but the truth is in there.

    - Tim.