Hey Guys - Cheers for the Current Replies. @filipp-sudanov said in Per User Tool Authentication: Hi! There is no such thing in netxms - we do no cache the password entered by user so we do not have it anywhere after user logs in. And it seems to be not good idea from security viewpoint to keep any passwords plaintext and enter them somewhere. Filipp - TY for the Info.  The current issue faced is that with trying to automate the tools as it stands - the only way is Clear text Custom Attributes - which is obviously no good, or manual entry every time - which takes up 2-10 seconds every connect to type/find password.  This adds up over a day/week/month/year and am just looking to increase productivity and reporting with XMS. The thought I had was that if the obscured field used to login was held in memory (an possibly encrypted) - then a call could be made to that whenever it was required @staj said in Per User Tool Authentication: Is PowerShell an option in your environment? Staj. Powershell is available I suppose - as to whether it's and option or not would come down to what Powershell would be used for.  If you have an Idea - I am all ears.  Would be happy to run external script if it means that overall (for everyone else not using in this way) XMS is a little more robust and secure. In the meantime - I have a couple of Ideas for what XMS could do to lessen my issue - so might just put in a feature request and see where it gets to. Cheers

Thanks for your help!

Do you have an agent inside that edgerouters network? Is there an IP upstream of that VPN connection that will respond to a ping? If the answer is yes to those two questions, you can setup an Icmp Target on that agent and collect the icmp data as a table dci. Make sure ping subagent is configured in the agents config file. add an icmp target to an address on the other side of the vpn connection. RESTART the agent Run configuration poll on node Create table dci from agent table

Something in cluster operation seems to be broken. We will check the code.

I'm using 3.4.284 on CentOS 8

Yes, in case of tunnel NetXMS does not store the IP address. The thing is that IP address from which the tunnel connection arrives is not necessary the IP of the node - it can be a NAT, etc. And if we take list of interfaces for a node - the could be several interfaces and we don't know which one is primary. You could get list of interfaces via NXSL script - the script should filter out loopback interface and if there are several interfaces - select one of them. There is currently no hook script on tunnel connection, you can run your script from configuration poll hook. Here's an example script that prints list of interfaces: for(i : $node->interfaces) { println i->name; for(a : i->ipAddressList) println " " . a->address . "/" . a->mask; } Also, there's a system event SYS_TUNNEL_OPEN - this event occurs when the tunnel is established, in the context of that node. So you can create a rule in EPP and run some script from there. It's not possible to update node's IP address from script, but you can create a cusome attribute on node and keep IP address there.

As an option you could look into script thresholds - this way you could check all you need with a help of NXSL script and generate event only when there is a problem.

@victor said in Netxms tomcat .war deploy: /var/lib/tomcat8/webapps is where application is deployed. But working directories for applications are in /var/lib/tomcat8/work/Catalina/localhost - try to delete them. Best regards, Victor Thank You Victor, exactly like you write, after delete catalina work dir and start tomcat again new UI is up and running. Problem solved.

Hi, they match. If %6 expands to empty string it means that "instance" attributre in DCI is not set. Are those DCIs created by instance discovery or manually? If manually, did you set "instance" field? Best regards, Victor

To search by ID you can use filter in object tree and type object id prepended by #, e.g. #258

Thanks, Victor. I appreciate all the work you guys are doing!

I figured out. I had to edit the src/java/netxms-eclipse/Core/plugin.xml file (the aboutText property).

Hi! Thanks for the clarification! The problem was that I only added the trusted CA to my Windows account and not the system. After I did the latter, it worked fine. Regards

We have lift off - Everyday that you learn something is a good day !!! - Thank you for your help & assistance  - much appreciated

The issue regarding "This DCI was added by instance ...." should have been fixed in current development branch and will be included in next patch release. The message is informative only so it does not affect functionality.

Hi, pay attention to case - it is modifyObject, not modifyobject. Best regards, Victor

It was caused by a bug in DB init script (wrong primary key). We have fixed it, fix will be included into next patch release. Best regards, Victor

That sounds useful, I've registered it as feature request (https://track.radensolutions.com/issue/NX-1911). Best regards, Victor

Yes, persistent storage (or custom attribute on a node) that holds timestamp of last SYS_NODE_DOWN would be best solution. Best regards, Victor

At the moment, we're doing another pass on expanding our use of NetXMS given it's new features since the last time we did so (which was a while ago). What I am interested in is sharing some of the stuff we're doing, will continue that on another thread though.