we are evaluating Confluence and Jira as new tools for our software-devlopement. We solved nearly all problems, as long as the users are in our internal network. We want to use a secure 2-factor authentication for external access to this services for external developers. We tried to use the "Portal" feature from a Fortigate-Appliance (which is in fact some kind of reverse proxy), but ran into a lot of troubles. Basically it's working, but some features don't. E.g. in Confluence the Rich Text Editor isn't working (nothing is happening if we try to switch to this edit mode). Another problem exists in Jira with the "Create issue" button in the upper right corner (it's resetting the URL).
I think it's somehow related with ajax-reloads used for this functions. When using the "Portal" function of the Fortigate-Appliance, it creates a kind of Forwarding-URL like https://external.domain.com/proxy/http/jira.domain.loc/secure/Dashboard.jspa (jira.domain.loc is the internal address of jira, same with confluence.domain.loc)
With Jira it's possible to see the problem within the URL. The URL in the address bar of the browser is rewritten to something like https://external.domain.com/secure/CreateIssue.jspa?pid=10000&issuetype=7&Create=Create. As you can see, the entire proxy part is missing.
We also tried a similar feature implemeneted into a Checkpoint-Appliance and it has the same issues.
Any help or experiences with this matter would be very appreciated.
Thanks in advance!
unfortunately this won't work - check
If you really need your Fortinet or Checkpoint to protect JIRA/Confluence, the only option I could think of is fronting JIRA and Confluence with Apache and the extensivly usage of mod_rewrite.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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