nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Tomcat monitoring

Fidelito Obcemia

Hi,

We would like to monitor the JIRA nodes and Tomcat.
We are using Manage Engine (ME) to monitor the nodes.

We also would like to monitor the Tomcat but whenever Manage Engine gets data from the nodes, it can't get through as JIRA is automatically prompting for a login. Thus, ME cannot get data from the nodes.

Is there any way we can skip the redirection to login prompt whenever connecting to JIRA for specific purpose like ME monitoring for Tomcat?

Please let me know any pointers.

Thanks

Accepted answers

All comments

Humashankar VJ

Hi @Fidelito Obcemia

To ensure clarity and security, adopt a refined approach to configure access control:

Firstly, modify server.xml using the <Valve> element to bypass authentication for specified IP addresses. Instead of using multiple valves, utilize a single <RemoteAddrValve> or <RemoteHostValve> to list allowed IPs:

This configuration grants access only to requests from specified IPs (e.g., Manage Engine server), blocking all other IPs from unauthenticated access.

Consider security implications carefully:

Ensure only non-sensitive endpoints are accessible without login.
Configure your reverse proxy or firewall to allow Manage Engine's IP to access designated endpoints.

For granular URL pattern control (optional), configure web.xml:

- Map specific URLs required by Manage Engine, bypassing authentication only for those endpoints.

<security-constraint>

<web-resource-collection>

<web-resource-name>MonitoringEndpoints</web-resource-name>

<url-pattern>/monitoring/*</url-pattern>

</web-resource-collection>

<auth-constraint>

</auth-constraint>

</security-constraint>

Finally, restart Jira to apply changes made to server.xml or web.xml.

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

Fidelito Obcemia

Hi @Humashankar VJ ,
Thanks for the pointers.
I will have a try and let you know.

Thanks again.

Much appreciated.

Cheers,

Fidelito Obcemia

Hi @Humashankar VJ ,
I have tried the setup on JIRA server's server.xml as to;

There are 2 valve setups, another one is;

As well as in JIRA server's web.xml as to;

<security-constraint>
<web-resource-collection>
<web-resource-name>MonitoringEndpoints</web-resource-name>
<url-pattern>/manager/status*</url-pattern>
<url-pattern>/manager/jmxproxy*</url-pattern>
</web-resource-collection>
<auth-constraint>

</auth-constraint>
</security-constraint>

But doesn't seem to work. I am getting connection refused from the Manage Engine server invoking the URL (e.g. https://JIRA_IP:PORT/manager/jmxproxy?qry=*:type=DataSource,*). URL should be https://JIRA_IP:PORT/manager/jmxproxy*

And sometimes, not able to open up the JIRA webclient (HTTP error 403).

And also still prompting with logon prompt. It is not bypassing the user logon prompt.

Can you please let me know your comments.

Thanks,

Fidelito

There are 2 Valve setups, another one is;

Humashankar VJ

Hi @Fidelito Obcemia

To enhance security, modify your server.xml and web.xml files. First, update server.xml to restrict access to specific IP addresses, including your ManageEngine server, using a single <Valve> element:

Add the following line, replacing <ManageEngine_IP> with your ManageEngine server's IP address:

Next, configure web.xml to allow unauthenticated access to select URLs required by ManageEngine. Apply security constraints to specific paths using:

<security-constraint>

<web-resource-collection>

<web-resource-name>MonitoringEndpoints</web-resource-name>

<url-pattern>/monitoring/*</url-pattern>

</web-resource-collection>

<auth-constraint>

</auth-constraint>

</security-constraint>

This setup restricts access based on IP in server.xml and allows unauthenticated access to only specified monitoring endpoints in web.xml.

Restart Jira after applying these configurations and confirm the outcome.

Regards

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center