[ZBX-26913] Zabbix JMX jira DataCenter template configuration with authentication Created: 2025 Aug 25  Updated: 2025 Sep 05  Resolved: 2025 Sep 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Hubert Rzyha Assignee: Unassigned
Resolution: Commercial support required Votes: 0
Labels: jira, template
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2025-08-25-17-36-40-298.png     PNG File image-2025-08-25-17-39-35-256.png     PNG File image-2025-09-04-15-31-40-582.png     PNG File image-2025-09-04-15-33-39-718.png    

 Description   

Steps to reproduce:

  1. addHost 
  2. Link it with Jira Data Center by JMX
  3. Zabbix Java gateway is installed on server
  4. Zabbix agent is installed on Jira done
  5. Configuration on Jira setenv: 
JAVA_OPTS="-Dcom.sun.management.jmxremote ${JAVA_OPTS}"
JAVA_OPTS="-Dcom.sun.management.jmxremote.port=8099 ${JAVA_OPTS}"
JAVA_OPTS="-Dcom.sun.management.jmxremote.local.only=false ${JAVA_OPTS}"
JAVA_OPTS="-Dcom.sun.management.jmxremote.ssl=false ${JAVA_OPTS}"export JAVA_OPTSCATALINA_OPTS="-Xms${JVM_MINIMUM_MEMORY} -Xmx${JVM_MAXIMUM_MEMORY} ${CATALINA_OPTS}"CATALINA_OPTS="-Dcom.sun.management.jmxremote.authenticate=true ${CATALINA_OPTS}"CATALINA_OPTS="-Dcom.sun.management.jmxremote.password.file=/opt/appdata/jira-home/jmxremote.password ${CATALINA_OPTS}"
CATALINA_OPTS="-Dcom.sun.management.jmxremote.access.file=/opt/appdata/jira-home/jmxremote.access ${CATALINA_OPTS}"
  1. . on template we have

Result:

Expected:
Everything works fine when I set authentication=false but we would like to enable it on prod environment.

 Comments   
Comment by Alexey Pustovalov [ 2025 Aug 26 ]

Please try to use http://docs.oracle.com/javase/8/docs/technotes/guides/management/jconsole.html and retrieve any JMX counter.

Comment by Hubert Rzyha [ 2025 Aug 26 ]

Can you tell me exactly how to do this and what you mean?
As I said the other node works correctly when authentication is set to false.  

Comment by Alexey Pustovalov [ 2025 Aug 28 ]

I mean try to use external tool to retrieve required data with enabled authentication.

Comment by Hubert Rzyha [ 2025 Aug 28 ]

dotneft 

Okay will try to do this. 

Comment by Hubert Rzyha [ 2025 Sep 04 ]

Hi dotneft 
I've tried to connect to Jira node where we have authentication enabled 

and got this: 

But when I tried to Jira node where authentication is set to false everything works fine. 
Can you tell me what I'm doing wrong: 

Comment by Alexey Pustovalov [ 2025 Sep 04 ]

You did not attach pictures.

Comment by Hubert Rzyha [ 2025 Sep 04 ]

 

Comment by Hubert Rzyha [ 2025 Sep 04 ]

Comment by Hubert Rzyha [ 2025 Sep 04 ]

pictures attached: first is where we have authentication off (set to false) and second where is enable (true) 

Comment by Alexey Pustovalov [ 2025 Sep 04 ]

So using different tool it does not work as well?

Comment by Hubert Rzyha [ 2025 Sep 04 ]

dotneft short answer is yes. 
Long answer is we are not sure what username we should use to authenticate - we set everything as default in jmxremote.password file and jmxremote.access - we only changed password. We believe username is controlRole but maybe not or we need to define somewhere. 
We checked documentation but it's not clear - does role means username? you can see from jconsole that error is connection failed: retry but from zabbix we can see invalid username or password. Connection is for sure open because we can connect to both nodes using zabbix or jconsole when authentication is disabled. 

Comment by Alexey Pustovalov [ 2025 Sep 05 ]

Everything depends on software configuration, it is better to consult with Java software vendor. Sorry, but such issue can not be qualified as Zabbix software issue / bug, so please reach out to [email protected] for commercial support (https://zabbix.com/support) or consultancy services.
Alternatively, you can also use community forum (https://www.zabbix.com/forum) for assistance.
With that said, we are closing this ticket. Thank you for understanding.

Generated at Fri Sep 12 22:02:24 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.