Hi Madhavi,
Within the native Jira application there really is not any means to restrict what addresses that Jira will accept connections from. However Jira does run within Apache Tomcat. And Tomcat does have some means to restrict this in a sense. Check out the KB How to Restrict Access to JIRA with Tomcat.
It explains two different means by which you can restrict network access to Jira. The first solution just sets Jira to only listen to a specific address. On servers with multiple addresses/interfaces, this could be useful a means to restrict network addresses, but only if you know that the address you set for Jira is only accessible by the group of addresses you want to allow.
The second option provides a level of remote IP filtering. From the way you describe this, it seems like it might be feasible solution. There is an updated Tomcat documentation link you could use to implement this in current Jira versions in http://tomcat.apache.org/tomcat-8.5-doc/config/valve.html#Remote_Address_Valve
You could also implement this kind of network restriction via routing rules on an edge device such as a router, firewall, etc. But the specifics of the configuration for that would be very dependent upon your environment, and in turn would not be something Jira would directly be managing.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.