- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2022 12:57 AM
Hi,
I'm trying to reach this article
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535650
But it says:
Solved! Go to Solution.
- Labels:
-
Knowledge Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2022 02:18 AM
Hi
What was the Article about.? When I searched I couldn't find anything but you can drop them a feedback and ask for alternate KB Article. Mark my answer as correct if that helps.
Regards,
Musab

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2022 02:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2022 04:08 AM
Hi
It's about validating SSH on the application server for on-prem implementation.
I'll follow your advice on reporting back to SN team.
Thanks,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2022 04:30 AM
This article is Retired as process was not validated. Same content is available on https://kinsta.com/knowledgebase/warning-remote-host-identification-has-changed/
Content on the article:
A need exists to be able to access application and database servers for testing.
Approach overview:
- Fix the known_hosts file without destroying all the existing RSA keys.
Change plan
- Using VI, run these commands in order on the file ".ssh/known_hosts"
- /string
(using example above, /db12345.abc1) - *dd
(ensure that your cursor is on the right line when running this) - :wq<enter>
(this saves and exits VI)
- /string
Test plan
- User should now be able to SSH into the server.
Document from ServiceNow: SSH credentials
If you need more help I suggest creating a Request with Support.