<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Try SSH credentials from a list? or auto discovery? failure notification?]]></title><description><![CDATA[<p dir="auto">Is there a way for NetXMS to try multiple credentials rather than just the single one stored in properties-&gt;communications-&gt;SSH?<br />
It's not feasible to enter credentials for every device manually, nor to manually change them periodically<br />
Most will use common LDAP username/password but many are individual. I'd like to create a list of all known credentials and it will try until it finds a match then stores it</p>
<p dir="auto">Is there a way to have a list of credentials and have NetXMS try each of them sequentially until it can successfully login? The same as SNMP credentials are enumerated until one is found, then store it<br />
(not enumerate the entire list every time a command is run, because it will generate a ton of invalid login attempt error messages)</p>
<p dir="auto">And if the password changes down the track and stored credentials are no longer valid, how can I have NetXMS notify me when I try and run scripts against a bunch of nodes that some of them failed because of incorrect details?</p>
]]></description><link>https://forum.netxms.org/topic/7276/try-ssh-credentials-from-a-list-or-auto-discovery-failure-notification</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 06:18:30 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7276.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 19 Jan 2022 07:39:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Try SSH credentials from a list? or auto discovery? failure notification? on Thu, 20 Jan 2022 20:19:37 GMT]]></title><description><![CDATA[<p dir="auto">Currently it is not possible. I think we should add SSH probe as part of configuration poll and handle it in a same way as SNMP credentials. It will also allow to generate relevant event when SSH is no longer responding.<br />
You may also try SSH authentication with private key - depending on your procedures it could be easier to just distribute key for NetXMS server once.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/30941</link><guid isPermaLink="true">https://forum.netxms.org/post/30941</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 20 Jan 2022 20:19:37 GMT</pubDate></item></channel></rss>