Connection
It's a key configuration in synchronization. It defines the target and / or source JIRA. All changes are pushed to or pulled from the target JIRA instance.
Connection consists of:
Name - which won't be visible in remote instance, but it's mandatory for synchronization (target of synchronization)
Remote URL - point to remote JIRA instance (it is not required if you select passive instance flag)
Technical User - it is the local JIRA user, defined in Technical User section
Local Authentication Key - it's token base solution, only data send with proper key will be synchronized, so it prevent unauthorized access to plugin API. We do recommend to use key matching your password policy. This value has to be unique, because it defines explicit connection on incoming request
Remote Authentication Key - it's token that allows access to remote JIRA instance (it's local authentication key set on remote instance)
Passive Instance - it sets communication model between passive and active, read more on Communication Models.
Often set when remote JIRA is behind firewall, so your local instance cannot send data to remote instance. In such case we turn passive instance flag on the other side (the instance not accessible / behind firewall need to stay active).
If you check it, remote URL and remote authentication key will not be required any more and that's because communication responsibility has been moved to active instance (active instance performs all requests in order to keep issues synchronized).
Please be sure that if you need active instance you can reach remote instance, and there is an exception in firewall, to avoid infrastructure problems not related with plugin.
If you fill all necessary data you can:
Test Connection (Remote JIRA test call) - to check if remote JIRA is accessible and we can connect to it. This call is skipped if connection is in passive mode. This test can also fail if remote JIRA is not set or is inaccessible.
Add connection - add connection, because dual configuration (to finish configuration you have to set proper connection on both JIRA instances), you can add connection without testing.
Expand | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
|