You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We recently made the decision to migrate from Jira server to Jira Cloud. While using Jira Server, we integrated with an application that was closed to the outside. This app works on-premis and can only be accessed internally. Naturally, when we were going to switch to Jira Cloud, it was necessary to allow the ip ranges that Jira came to our application through the Firewall.
We found this document while researching these ip ranges. We allowed all the ip addresses in the document, but the REST operations we made to our application via Jira Cloud failed.
However, we wanted to try it in a different way. We opened our application completely to the outside and we wanted to see Jira, with which ip address it came to our on-premis application. As a result of our 4 different rest operations, we determined that Jira came to our local application from the following ip addresses.
However, these ip addresses are not defined in the ip ranges document. In addition, it is not defined in AWS's ip ranges. That's why even allowing a large number of thread spacings in the relevant document does not solve it.
We opened a ticket to Atlassian regarding the case, but they could not provide a solution. Have you experienced similar situation? Has anyone tried accessing the application in the internal network via Jira Cloud and succeeded? If yes, can you help us on how to do it?
Thank you very much for the information you have provided.
As you mentioned, it will be necessary to automate the definition of permissions over the ip. However, we have doubts about whether the ip ranges are up to date.
We have decided to use a tunnel server in this case. This structure will work like the Proxy method you mentioned. We will install Apache on the tunnel server. Jira cloud will make a request directly to the tunnel server. The tunnel server will check the incoming requests and send the valid ones to our application server.
In this way, we think that it will be sufficient to allow only the tunnel server to the Firewall rules on our application server.