Securing the Jira application provided by the firewall gives a sense of security. The software “behind the firewall” is unavailable and unreachable in the network, which effectively increases the level of data protection. The perfect solution, but what if we want to connect to such an application from the outside?
What is a firewall?
A firewall is one of the ways to ensure security at the network level. Its task is to protect the equipment and the local computer network against access from the so-called public network. It prevents outflow of data and filters incoming and outgoing connections, thanks that controlling access to the internal network. In addition, the firewall monitors traffic and logs events, which helps administrators to recognize attacks and improve configuration.
How to connect?
With such security as it is difficult to connect with the outside world. However, it is possible thanks to the implementation of an appropriate solution.
For example, let say that we have two Jira instances. We keep confidential data on one that is behind a firewall. The second public is for us to work with an external client. We really care about security, but at the same time we would like to combine these two instances to replicate some information or update it.
The solution to this problem is installation IssueSYNC. Thanks to apps, we can connect two instances of Jira. In the case when one application is in the firewall, after the implementation, it becomes an active instance and the other, visible in the public network – passive.
The answer is partly in the nomenclature we adopted:
- The passive instance does not perform any activities related to establishing a connection.
- The active instance takes over the transmission of all communication, both incoming and outgoing.
The active instance is always on the server behind the Firewall because only it can establish a connection with the outside world to which it’s invisible.
How it is work?
- The communication process between Jira applications
An active instance sends its changes as if we were integrating two active instances. At the same time, it establishes another connection with the passive one to check if there are any pending changes applied to it.The disadvantage of this solution is higher delays in transmitting changes from a passive instance because it cannot send them immediately. The instance has to wait to report for them actively. However, we are talking about an extra minute or two. It should also be noted that the lack of changes in the active instance does not affect the frequency of retrieving data from the passive instance. It is an independent process.
- Configuration replacement
IssueSYNC lists some configuration items between two Jira instances, e.g., field names or workflow transitions. Also, the fact that one instance is behind a firewall is not an obstacle to the exchange of this information in a similar way of exchanging data between applications.
The solution I have presented will allow you to create a connection between the Jira application behind the firewall and the other in the public network, while maintaining the same level of security. Thanks to IssueSYNC, you can quickly synchronize all information on them.