Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,880
Community Members
 
Community Events
165
Community Groups

How to restrict FishEye access to dedicated IP addresses

We're running FishEye/Crucible on a productive server and want to allow access to it from only a number of dedicated IP addresses (e.g. the reverse proxy).

The built-in Jetty could be configured suitably by altering the jetty.xml, but this file does not exist and FishEye/Crucible seems to configure it programmatically.

So is there a way to achieve this?

2 answers

1 accepted

3 votes
Answer accepted

Aside from configuring application link ip patterns as Janet has suggested; you could configure the iptables/windows firewall on your Fisheye server to only accept port 8060 requests from your reverse proxy ip.

Deleted user Jan 20, 2013

We run all the applications behind Apache HTTPD reverse proxies. If it were also the case here, it would be simple to configure access to the proxy from the web server and manage direct access to the specific port numbers by firewalling (iptables).

0 votes
Janet Albion Atlassian Team Jan 20, 2013

Have you tried setting the IP Patterns in the Application Links ? It's should be via Administrations > Application Links > Configure > Incoming Authentications

Look at https://confluence.atlassian.com/display/FISHEYE/Configuring+Trusted+Applications+Authentication+for+an+Application+Link

So the recommended way is to link FishEye with for example JIRA and configure the incoming authentication in that link?

I was thinking that this would only affect access to the FishEye remote API.

But if it applies to access in general including web access via browser this would do the trick for us, as we are also running an instance of JIRA we can link to.

I think you are correct, trusted applications only controls access from the remote APIs rather than client access from a browser. I'm not aware of a way of locking down Fisheye access to one IP address other than with iptables/firewall.

If that is true, we will most likely come back to your iptables solution.

I was just wondering if there was some built-in solution as it seemed to me a pretty common configuration.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

235 views 1 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you