SSH Discovery Credential not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Team,
We created a service account (SSH Private Key), for which some Linux devices are getting discovered using this account.
But it is not getting utilized for rest of the Linux servers. Below are the discovery logs.
What are the steps to resolve this issue? Can you please guide?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
I would ask the Linux team to investigate but the very first thing to try is direct ssh (from your computer not ServiceNow) into this system with the username/password discovery is trying to use. If that fails then it's a very easy handover to the Linux admins to ask why that account can't log in (common reasons would be invalid home directory or shell, the former being the most likely).
Just to be clear, the username and password _might_ be valid on that system but if the shell binary isn't on it or it is but cannot change to the home directory then the login will fail. ServiceNow doesn't differentiate these - it's just a login failure and it tells you the credentials didn't work.
It's possible you could see the true error in the ECC logs but it will be very clear if you try a manual ssh connection (depending what you're using to test from - PuTTy is a common tool used for this on Windows systems, Linux systems will naturally have an "ssh" command).