Can Exalate be used on 2 different customers' Jira instances to sync only specific scopes, without compromising/exposing the security of any other "project" they don't want to sync on both sides? Any other project must be unavailable from the other party

Use Case
, ,
1

Originally asked by Vincent Kopa (Ovyka) on 11 August 2021 (original question)

e.g. when using Exalate on 2 different customers’s Jira instances, and they do not want to expose the tickets of any other project.

Can Exalate cause a kind of “backdoor” for customer A to access all data from customer B’s Jira through the connection between these two plugins ?

What are the limitations for this ? Can Exalate be used to only expose very specific data on each connection, without allowing the other party to “pry around” (seeing the list of other projects, other fields etc.)

2

Answer by Mariia Onyshchenko on 12 August 2021

Hi Vincent Kopa (Ovyka) ,

If Visual Mode is used, then you have one account, that must be admin on both sides. But if they use Script Mode, then all data is 100% secure and not reachable by the other side.

Comments:

Vincent Kopa (Ovyka) commented on 12 August 2021

Thank you Mariia !

3

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.