OSLC Connect for Jira Cloud - Architecture & Network Topology

Architecture & Network Topology

OSLC Connect for Jira Cloud enables integration between Atlassian Jira Cloud and other OSLC-compliant tools. The installation consists of the following components:

Forge App: An Atlassian Forge application that runs within Jira Cloud and provides the user interface integration.
OAuth Integration App: Handles OAuth 2.0 authentication between Jira Cloud and the Broker.
Broker: A server-side component that manages OSLC communication and stores settings in a PostgreSQL database.

The diagram below illustrates how the different components are organized and how they communicate with each other across network boundaries.

Network architecture diagram of OSLC Connect for Jira Cloud

The architecture spans three network zones:

Internet (Jira Cloud): Atlassian hosts the Jira Cloud platform, which exposes the Jira REST APIs and runs the OSLC Connect Forge App. The Forge App provides the user-facing integration within Jira Cloud.
Internet or Enterprise network (OSLC Broker): The OSLC Connect Web Application is deployed in a Tomcat Servlet Container. It acts as the central hub, communicating with Jira Cloud on one side and with the OSLC Remote Applications on the other. It stores its configuration data in a PostgreSQL database.
Enterprise network (OSLC Remote Applications): The OSLC-compliant tools you want to integrate with Jira, such as IBM Engineering Lifecycle Management (ELM), Siemens Polarion, or other OSLC-compatible applications, reside on the enterprise network.

All communications between the Broker and the other components (Jira Cloud and OSLC Remote Applications) are performed over HTTP requests. This means the Broker must have network accessibility to both Jira Cloud (over the Internet) and the OSLC Remote Applications (on the enterprise network). Make sure that firewalls and network policies allow these connections.