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?
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).
Have you tried setting the IP Patterns in the Application Links ? It's should be via Administrations > Application Links > Configure > Incoming Authentications
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.
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...
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