1.1 Detailed Technical Requirements
new version
The technical requirements for the add-in differ from device to device.
| Classical Windows Add-in | Modern Office Add-in | |
|---|---|---|
| Windows | - Outlook 2010, 2013, 2016 - .net Framework 4.5 - JIRA 6.0 or higher | - Outlook 2013, 2016 - Office 365 subscription or Exchange Server 2016 CU5 |
| Mac | n/a | - Outlook 2016, at least version 15.37 - Office 365 subscription or Exchange Server 2016 CU5 |
| Web | n/a | - Office 365 subscription or Exchange Server 2016 CU5 |
| Android | n/a | - Outlook Mobile App - Office 365 subscription |
| iOS | n/a | - Outlook Mobile App - Office 365 subscription |
Jira Cloud | Supported via direct connection 🔒 | Supported via cloud connect 🌍 |
| Jira Server | Supported via direct connection 🔒 💡 Some SSO solutions may require additional configuration | Supported via direct connection if system uses SSL (https) 🔒 Supported via cloud connect if system is publicly accessible 🌍 NOT supported, when http and private 💡 Some SSO solutions may require additional configuration |
Connection Types
🔒 Direct Connection
If technically possible, our add-in tries to establish a direct connection to the Jira system. This is always possible when using the classic Windows add-in, as it runs locally on the users computer and can open outgoing connections.
The modern add-in always runs in a browser context, even when used in the desktop & mobile versions of Outlook. Therefore it's subject to all restrictions of normal web apps. As Jira does not send CORS headers in a consistent and reliable manner, we need to rely on some other techniques.
Jira Server / Data-Center connection in modern add-in
When using our Jira for Outlook add-on on Jira Server, we have the possibility to extend Jira to a certain point. This allows us to use a direct connection, if the Jira is secured via SSL.
We do this by using embedding a webpage of our add-on in Jira in Outlook, which is allowed to communicate with Jira.
.png?version=1&modificationDate=1534951113521&cacheVersion=1&api=v2&width=662&height=400)
For this to work, the following URL needs to be reachable without (
) authentication:
https://jira.my.corp/plugins/servlet/jiraforoutlook/proxy
Note: If you are using any SSO solution or reverse proxy, please make sure to add an exception for this site. Authentication will happen when calling the Jira REST API, this does not allow access to your Jira system. It just helps us establish a connection in the first place.
🌍 Cloud Connect
This applies to Jira Cloud systems and Jira server systems without SSL (not recommended). We cannot to these systems from the modern add-in directly, so we are using our "Cloud Connect Proxy".
.png?version=1&modificationDate=1534952432925&cacheVersion=1&api=v2&width=830&height=280)
Outlook will generate a one-time access token, based on your credentials and passes this token to our proxy. Please note that this token can only be used for a specific URL in Jira and can only be used one-time.
🔐 Security Info:
- We don't get permanent access to your system, since it's a one-time token
- We don't get in contact with your user credentials, everything is done via OAuth (requires the Jira add-in to be installed correctly)
- We don't store or log any information on this proxy, it's just a pass-trough system