At the moment we have Jira Service desk running on premise server internally.
We want to make the Jira service desk customer portal available to the internet so our external customers can create/view issues, without giving access to our internal service desk portal.
With security in mind we don’t want our internal service desk portal be accessible from the internet, but only from the intranet.
The only solution we found so far was to open the port of our Jira server for everything and everyone, however this means our internal portal login page is also reachable from the internet.
And that is not what we want.
I have not done this, but have few thoughts.
Jira doesn't run a separate port/instance for the ServiceDesk customer portal, so there is no way to do this if you are directly going to make your Jira instance face the internet.
But wouldn't suggest that anyway. You would be better off setting up some sort of proxy (or a Web Application firewall) to relay the communications between the internet and your Jira Server.
All the ServiceDesk Portal URL's start with https://<HOST>/servicedesk/customer so as long as that is the only URL prefix that you allow through the proxy, then you should be ok.
However, Jira itself will probably not like the fact that you will be using 2 different names to access it. It has lots of internal self references that work best if the name matches. You may need to do some additional configuration on your proxy to make this work well.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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