Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Core 8.5.1 through Fortigate VPN

We're running Jira Core 8.5.1 internally, but have a Fortigate 6.2.2 VPN in place for external users to access Jira.

Internally, Jira works perfectly fine.

However, through the VPN the initial Dashboard screen basically loads a blank page, drop downs (like the Projects dropdown) don't work unless you first go to your profile page, and even then the initial project display page won't show anything.  If I log in as an admin and look at workflows, none of my custom transitions or states will display, only the core Jira create, closed will show but with no transitions between, all sorts of things like that.

I have read several posts where people have had issues with jira through a vpn, and I guess I mainly need to understand what the main issue is so I can go back to my management to tell them if it's even going to be possible to make this work, or if it just will need to be internal and if someone wants to remotely use Jira, they'll need to RDP into a vm first.

When connecting via the VPN, our URLs end up looking like this:

https://<ip address of vpn server>:10443/proxy/0511f83d/https/<internal Jira server >/projects/CR/issues

Internally the URL would look like https://<internal Jira server >/projects/CR/issues

The 0511f83d is a session id that changes each time you log on. 

I tried updating our server.xml for our https connection to use proxyName and proxyPort of the VPN proxy, but that didn't do anything to help the VPN connection (and it caused the internal access to be all whacky because of baseURL issues).  

I've read through documentation on configuring Tomcat to work with proxies by setting proxyName/port, and updating the baseUrl to work with the proxy server instead, but I'm guessing because our baseURL changes every time with the session ID that using the Fortigate VPN with Jira will not work.

 

Any info or suggestions, even if it's validating that Jira will not work with this network setup, would be greatly appreciated.  

1 answer

Sorry to tell you, but this is not going to work. See also this thread.

Only thing that would work is to use the VPN client so users can login via their browser.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....

32 views 0 2
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