- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 12:44 AM
Hi All,
I have a question:
While discovered devices, i'm facing "No valid credential found for types [SSH Password,SSH Private Key,Azure SSH Certificate]" issue. Can anyone suggest what should be done to resolve the issue?
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 06:55 AM
Hi @GP001
This error is specific for Linux Devices. If you have created the SSH credentials and trying to discover them, its not able to autenticate with it.
You can also validate by testing the credentials from credentials page.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 10:33 PM
Hi @GP001 can you test the credentials of ssh what you have created if it is success. Their might be cause for this instead of single mid server apply for all the mid servers which are available in your instance while testing credentials.
To troubleshoot common issue in discovery I'm attaching KB below.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535181
Mark this helpfull. If it helps you to understand.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 06:55 AM
Hi @GP001
This error is specific for Linux Devices. If you have created the SSH credentials and trying to discover them, its not able to autenticate with it.
You can also validate by testing the credentials from credentials page.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2024 02:00 PM
Thank you @pratik0306
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 10:33 PM
Hi @GP001 can you test the credentials of ssh what you have created if it is success. Their might be cause for this instead of single mid server apply for all the mid servers which are available in your instance while testing credentials.
To troubleshoot common issue in discovery I'm attaching KB below.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535181
Mark this helpfull. If it helps you to understand.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2024 02:01 PM
Thank you @SK Chand Basha