Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - grae

Pages1
#1
General Support / Re: Jira Cloud Setup in 2023 - Help getting setup with 4.3.2 via atlassian webhooks
December 07, 2023, 06:05:55 PM
We're still awaiting if this is on the plan for 2024 at least?

Thank you!
#2
General Support / Re: NetXMS Grafana Plugin
December 07, 2023, 06:04:59 PM
Thanks Victor, please keep us in the loop!
#3
General Support / Re: Jira Cloud Setup in 2023 - Help getting setup with 4.3.2 via atlassian webhooks
June 21, 2023, 10:02:50 PM
Just checking back on this if there has been any update or if you are ready for us to try a test build?


Thank you!
#4
General Support / Re: Jira Cloud Setup in 2023 - Help getting setup with 4.3.2 via atlassian webhooks
April 27, 2023, 01:36:05 AM
Victor,
Thank you, yes we would be happy to run the test build. @graeChris just updated us to 4.3.5 so that's our current version.

Thank you
#5
General Support / Re: Jira Cloud Setup in 2023 - Help getting setup with 4.3.2 via atlassian webhooks
April 24, 2023, 01:42:22 AM
So after much research and digging I have found the problem.  
NetXMS makes requests to the following Jira Cloud Endpoints - 
https://yourdomain.atlassian.net
         /rest/auth/1/session
         /rest/api/2/myself

I was able to pull the Jira Cloud APIs into Postman and /auth/1 no longer was listed, (api/2 has also been replaced by 3.)  Apparently session is for a session cookie and Jira Deprecated this start back in 2019. So Atlassian has disabled this method and needs to be replaced by API Token (which is what I had tried before, I even tried encoding my username and password as BASE64 per the Jira docs)


Which APIs and methods will be restricted?
For the following APIs and pages, all requests using basic authentication with a non-API token credential will return 401 ( Unauthorized) after the deprecation period:
  • Jira Cloud public REST API
  • Jira Software public REST API
  • Jira Service Desk public REST API
  • All Jira Cloud web pages
The following Jira Cloud REST API endpoint will be removed:



Deprecation notice - Basic authentication with passwords and cookie-based authentication (atlassian.com)

Cookie-based auth for REST APIs (atlassian.com)


 


Hopefully, this can get on the patch list to swap those calls as it is now a broken feature.  Please let me know if there's anything I can do to help, I've spent considerable time troubleshooting this and logged all the info if needed.
#6
General Support / Jira Cloud Setup in 2023 - Help getting setup with 4.3.2 via atlassian webhooks
April 18, 2023, 01:44:42 AM
I've been trying to set up hdlink.jira and have followed what limited information is available.  I'm running the latest version 4.3.2 and found in the release notes of 4.1 that Jira Cloud is supposed to be supported. 

I've added a Webhook in Jira Cloud by going to System Settings, Webhook, creating a webhook named netxms with the URL pointing back to the 
https://netxmsserver.mydomain.com:8008/jira-webhook 
It's been given Issue, Comment, Attachment, create, updated, and deleted permissions.

However there is no way to set up authentication in Jira Cloud for webhooks, I tried creating and adding in an API key and using either netxms or my Jira [email protected] but that also failed.

Port 8008 is open to the internet 

Here are the settings I have in NetXms
 
NameValue
Jira.IssueTypeTask
Jira.Loginnetxms
Jira.Password
Jira.ProjectCodeMYPROJECT
Jira.ProjectComponent
Jira.ResolvedStatusDone
Jira.ServerURLhttps://mydomain.atlassian.net
Jira.Webhook.Path/jira-webhook
Jira.Webhook.Port8008


When running the server in Debug mode 6 I can see the following errors, 

Code Select
16:24:19.419
generic
2023.04.17 21:23:43.742 *D* [hdlink.jira        ] MicroHTTPD: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
16:24:19.419
generic
2023.04.17 21:23:43.744 *I* [hdlink.jira        ] Jira webhook initialized on port 8008
16:25:35.655
generic
2023.04.17 21:25:35.607 *D* [hdlink.jira        ] Jira login failed, HTTP response code 401
16:26:14.748
generic
2023.04.17 21:26:08.165 *D* [hdlink.jira        ] Jira connection check: HTTP response code is 401
16:26:14.757
generic
2023.04.17 21:26:08.458 *D* [hdlink.jira        ] Jira login failed, HTTP response code 401
16:26:14.757
generic
2023.04.17 21:26:08.458 *D* [hdlink.jira        ] Jira login failed, HTTP response code 401
16:29:43.053
generic
2023.04.17 21:29:42.339 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:29:43.110
generic
2023.04.17 21:29:42.786 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:29:43.120
generic
2023.04.17 21:29:42.985 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:29:44.168
generic
2023.04.17 21:29:43.405 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:30:13.402
generic
2023.04.17 21:30:12.427 *D* [hdlink.jira        ] Jira connection check: HTTP response code is 401
16:30:13.412
generic
2023.04.17 21:30:12.698 *D* [hdlink.jira        ] Jira login failed, HTTP response code 401
16:36:49.659
generic
2023.04.17 21:36:49.140 *D* [hdlink.jira        ] Jira webhook request: GET /
16:36:49.659
generic
2023.04.17 21:36:49.141 *D* [hdlink.jira        ] Response code 404 to webhook call
16:38:42.772
generic
2023.04.17 21:38:42.046 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:42:25.116
generic
2023.04.17 21:42:24.418 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:43:08.578
generic
2023.04.17 21:43:08.464 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
16:43:35.507
generic
2023.04.17 21:43:34.859 *D* [hdlink.jira        ] MicroHTTPD: Error processing request (HTTP response code is 400 ('<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection.
If I run the server with Debug level 7 I get a little bit more information
Code Select
2023.04.17 22:24:55.996 *D* [hdlink.jira        ] Jira webhook request: GET /jira-webhook
17:24:57.968
generic
2023.04.17 22:24:57.334 *D* [hdlink.jira        ]    Host: localhost:8008
17:24:57.968
generic
2023.04.17 22:24:57.334 *D* [hdlink.jira        ]    Connection: keep-alive
17:24:57.968
generic
2023.04.17 22:24:57.334 *D* [hdlink.jira        ]    sec-ch-ua: "Chromium";v="112", "Microsoft Edge";v="112", "Not:A-Brand";v="99"
17:24:57.968
generic
2023.04.17 22:24:57.335 *D* [hdlink.jira        ]    sec-ch-ua-mobile: ?0
17:24:57.968
generic
2023.04.17 22:24:57.336 *D* [hdlink.jira        ]    sec-ch-ua-platform: "Windows"
17:24:57.968
generic
2023.04.17 22:24:57.336 *D* [hdlink.jira        ]    DNT: 1
17:24:57.968
generic
2023.04.17 22:24:57.336 *D* [hdlink.jira        ]    Upgrade-Insecure-Requests: 1
17:24:57.969
generic
2023.04.17 22:24:57.336 *D* [hdlink.jira        ]    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48
17:24:57.970
generic
2023.04.17 22:24:57.382 *D* [hdlink.jira        ]    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
17:24:57.970
generic
2023.04.17 22:24:57.385 *D* [hdlink.jira        ]    Sec-Fetch-Site: none
17:24:57.972
generic
2023.04.17 22:24:57.386 *D* [hdlink.jira        ]    Sec-Fetch-Mode: navigate
17:24:57.972
generic
2023.04.17 22:24:57.386 *D* [hdlink.jira        ]    Sec-Fetch-User: ?1
17:24:57.972
generic
2023.04.17 22:24:57.386 *D* [hdlink.jira        ]    Sec-Fetch-Dest: document
17:24:57.972
generic
2023.04.17 22:24:57.387 *D* [hdlink.jira        ]    Accept-Encoding: gzip, deflate, br
17:24:57.972
generic
2023.04.17 22:24:57.388 *D* [hdlink.jira        ]    Accept-Language: en-US,en;q=0.9
17:24:57.972
generic
2023.04.17 22:24:57.388 *D* [hdlink.jira        ] Response code 405 to webhook call
17:28:04.000
generic
2023.04.17 22:28:03.009 *D* [hdlink.jira        ] MicroHTTPD: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
17:28:04.000
generic
2023.04.17 22:28:03.014 *I* [hdlink.jira        ] Jira webhook initialized on port 8008
Any assistance would be greatly appreciated.  Thank you
#7
Feature Requests / Re: ModBus TCP/IP
April 06, 2023, 01:02:18 AM
We too would be interested in ModBUS support, a lot of devices in the Utility industry are moving to this and would be huge to not to have to use a work around (found in the forums here but not tested).

#8
General Support / Anyway to make Proxy Nodes subnet aware in their zone
March 23, 2023, 09:15:21 PM
So it looks like proxy nodes are not subnet aware when added to a zone, what I mean by that is take the following

NetXMS Server Public WAN
All agents using agent to server tunnel configuration.

Zone A (with proxynodes 1 & 2 set under properties, communications, Proxy nodes)
Subnet 192.168.1.0/24
  • SNMPdevice1 - 192.168.1.2
  • ProxyNode1 - 192.168.1.3
  • WindowsAgent1 - 192.168.1.4

Subnet 172.16.16.0/24
  • SNMPdevice2 - 172.16.16.2
  • ProxyNode2 - 172.16.16.2
  • WindowsAgent2 - 172.16.16.2

Now in the console, I will randomly get device offline in each subnet, as though it appears to not have any defined or exposed method of selecting which ProxyNode is used for the subnet.  If I select SNMPDevice2 I can manually goto it's properties and choose Communications and specify the ProxyNode2 (thus overriding the Zone A defaults) and this clears the communications errors.

These Zones can be logical or physical separations, for example, different parts of a DMZ, or separate buildings / offices but still communicate back to say the same set of servers.  For example desktops in subnet 1 & 2 talk to servers in subnet3 but not each other.

My Question - 
Are the Proxy Nodes subnet aware and if not
Is there a way to set the communication Properties per subnet?  It seams selecting the subnet properties doesn't have that option and it would be a huge benefit (at least to me) to control communication via the subnet layer.

Thank You
#9
General Support / Re: After binding remote agent it loosed connection with tlsv1 a decrypt error - Win
March 17, 2023, 07:44:08 PM
Ok so I finally got it to connect, this morning I deleted everything, went line by line and here's what worked for me:

c:\NetXMS\Bin\openssl.exe
Code Select
openssl genrsa -out rootCA.key 2048
openssl req -config openssl.conf -x509 -new -key rootCA.key -days 10000 -out rootCA.crt
openssl genrsa -out server.key 2048
openssl req -config openssl.conf -new -key server.key -out server.csr
openssl x509 -req -in server.csr -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out server.crt -days 5000 -extfile openssl.conf -extensions v3_ca
I copied those certificates to c:\NetXMS\cert (I'm sure you could leave them in \bin if you wanted)

Then in my server configuration
c:\netxms\etc\netxmsd.conf
Code Select
# For agent tunnels
TrustedCertificate = C:\NetXMS\cert\rootCA.crt
TrustedCertificate = C:\NetXMS\cert\server.crt
ServerCertificate = C:\NetXMS\cert\server.crt
ServerCertificateKey = C:\NetXMS\cert\server.key
The trick was to add BOTH the rootCA.crt and the server.crt as TrustedCertificate
After rebooting the server it worked!

Some things that helped was running the server executable and setting debug 4, this helped me see the connection information.

Same thing on the client side, run the c:\netxms\bin\nxagentd.exe -D6
-D4 also worked, but client side D6 gave a little more, in addition setting "nxagentd.exe -S" stopped the service so it wouldn't auto restart and have to be killed.  Made it easier to diagnose.

Anyway hope this helps someone in the future, drove me crazy for hours!
#10
General Support / After binding remote agent it loosed connection with tlsv1 a decrypt error - Win
March 17, 2023, 12:38:30 AM
I just deployed NetXMS in azure on Server 2022, opened up port 4700 & 4703.
Created the self signed certificates

Code Select
openssl genrsa -out rootCA.key 2048
openssl req -config openssl.conf -x509 -new -key rootCA.key -days 10000 -out rootCA.crt
openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr -config openssl.conf

C:\NetXMS\bin>openssl x509 -req -in server.csr -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out server.crt -days 5000 -extfile openssl.conf -extensions v3_ca
Finally my agents will show up in Agent Tunnels as Unbound, however as soon as they are bound, it will close and reset the tunnel, load new certificates and then error out with the error  SSL routines::tlsv1 alert decrypt error
Code Select
2023.03.16 17:25:52.864 *W* [                   ] Tunnel with XXX.XXX.XXX.XXX closed
2023.03.16 17:26:12.565 *D* [tunnel             ] XXX.XXX.XXX.XXX: Resetting tunnel
2023.03.16 17:26:12.630 *D* [tunnel             ] XXX.XXX.XXX.XXX: Loading certificate from file
2023.03.16 17:26:12.634 *D* [tunnel             ] XXX.XXX.XXX.XXX: Certificate and private key loaded
2023.03.16 17:26:12.776 *D* [tunnel             ] XXX.XXX.XXX.XXX: TLS handshake failed (error:00000001:lib(0)::reason(1))
2023.03.16 17:26:12.777 *D* [tunnel             ] XXX.XXX.XXX.XXX: Caused by: error:0A00041B:SSL routines::tlsv1 alert decrypt error
After a few minutes it times out and ignores the certificate, and shows back up as un-bound in the console.  Any help is greatly appreciated as this will never be used over LAN or VPN and must be able to register and manage remote sites.
Code Select
2023.03.16 17:30:44.891 *D* [tunnel             ] XXX.XXX.XXX.XXX: Next connection attempt will ignore agent certificate
2023.03.16 17:31:15.106 *D* [tunnel             ] XXX.XXX.XXX.XXX: TLS handshake completed
2023.03.16 17:31:15.107 *D* [tunnel             ] XXX.XXX.XXX.XXX: Server certificate subject is C=US,ST=WY,L=Cheyenne,O=Grae Inc,CN=Grae Network Monitoring
2023.03.16 17:31:15.107 *D* [tunnel             ] XXX.XXX.XXX.XXX: Server certificate issuer is C=US,ST=WY,L=Cheyenne,O=Grae Inc,CN=Grae Network Monitoring
2023.03.16 17:31:15.108 *D* [tunnel             ] XXX.XXX.XXX.XXX: Server certificate verification is disabled
2023.03.16 17:31:15.108 *D* [tunnel             ] XXX.XXX.XXX.XXX: Server certificate pinning is disabled
2023.03.16 17:31:15.108 *D* [comm.vs.3          ] Requesting metric "System.PlatformName"
2023.03.16 17:31:15.110 *D* [comm.vs.3          ] Requesting metric "System.UName"
2023.03.16 17:31:15.110 *D* [comm.vs.3          ] Requesting list "Net.InterfaceList"
2023.03.16 17:31:15.118 *D* [tunnel             ] XXX.XXX.XXX.XXX: Sending message CMD_SETUP_AGENT_TUNNEL (1)
2023.03.16 17:31:15.293 *D* [tunnel             ] XXX.XXX.XXX.XXX: Received message CMD_REQUEST_COMPLETED (1)
2023.03.16 17:31:15.293 *I* [                   ] Tunnel with XXX.XXX.XXX.XXX established
2023.03.16 17:31:15.294 *D* [tunnel             ] XXX.XXX.XXX.XXX: Tunnel is active
2023.03.16 17:31:45.302 *D* [tunnel             ] XXX.XXX.XXX.XXX: Sending message CMD_KEEPALIVE (2)
2023.03.16 17:31:45.375 *D* [tunnel             ] XXX.XXX.XXX.XXX: Received message CMD_KEEPALIVE (2)
2023.03.16 17:32:10.015 *D* [websvc             ] WebServiceHousekeeper(): running cache entry check
Pages1