-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
6
-
We need to provide our customers with more information on the architecture details of how the Jira Server for Microsoft Teams plugin work.
The document we currently have in the link: https://www.msteams-atlassian.com/JiraServer/ is very abstract and doesn't give any insight on how the plugin works.
We need to have some architecture diagrams to show how the plugin connects to Microsoft teams and what are the services that work in between Jira and the Microsoft Teams.
Having a clear block diagram would help very much in describing the architecture.
We would need to identify all the Azure services that will directly interface with the plugin on the customer side, Identifying their IP address ranges and their function.
Also the document: https://www.msteams-atlassian.com/JiraServer/ requests the customer to white list a large list of IPs, it doesn't tell why those needs to be white-listed and what are the hosts/services that correspond to those IPs which makes the job of justifying those white-lists difficult.
Moreover for customer using an outbound proxy, the documentation must be adjusted as well. The outbound proxy configuration must be adjusted to allow Jira to reach those IP through outbound proxy.
It is unclear also that it is a bidirectional integration between the Jira server itself and the Teams application. Jira needs to communicate to the following endpoints (plus a few additional others), but these same endpoints/networks also need to communicate with Jira:
Hopefully the last sentence of the description that was added by Isabel yesterday (Oct 14th 2021) is not true, because our DataCenter System is absolutely not reachable from the internet, and so also the 3 mentioned URL's cant reach our on premise hosted DataCenter Instance.
And I believe that it is not true, because otherwise we would not be able to use the Integration from MS Teams side at all. But this is possible even the known problems (bad performance, custom field type not supported on create screen , missing configuration options for issue display in single and list view,, etc)