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?
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.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs