1. Security Considerations
February 15, 2015
Proprietary and Confidential, zAgile, Inc.

2. zAgileConnect Prerequisites
Connectivity between Salesforce and JIRA
zAgileConnect Salesforce App
zAgileConnect JIRA Plugin
OAuth
REST over HTTPS
OAuth
Active Objects
Components:
Salesforce App (AppExchange)
JIRA plugin (Atlassian Marketplace)
On-premise JIRA (Version 6.x)
HTTPS connection between Salesforce and JIRA
Proprietary and Confidential, zAgile, Inc.

3. zAgileConnect Authentication
Salesforce to JIRA
Requires JIRA SSL port accessible to Salesforce whitelisted IP addresses
Uses OAuth token to authenticate all transactions from Salesforce to JIRA
Communication over HTTPS
All actions performed in JIRA on behalf of Salesforce users are restricted at Project and Issue Level with following precedence:
first using privileges defined for that user in JIRA, if Salesforce user has an account in JIRA
else using privileges defined for ‘Integration User’ in JIRA, if Salesforce user does not have an account in JIRA
Requires JIRA URL to be defined as Remote Site in Salesforce
Salesforce App communicates with zAgileConnect JIRA plugin, as well as JIRA via REST API
Proprietary and Confidential, zAgile, Inc.

4. zAgileConnect Authentication
JIRA to Salesforce
Uses OAuth for authenticating all transactions from JIRA to Salesforce
JIRA defined in Salesforce as ‘Connected App’ with the following options:
Full Access
Perform requests on your behalf at any time
‘Consumer key’ and ‘Consumer secret’ tokens for Connected App stored in JIRA Application Properties
Salesforce ‘Integration User’ account used to log in to Salesforce using the above tokens to generate Authentication token (also stored in JIRA Application Properties)
Authentication token used with each REST call from JIRA to Salesforce
Communication over HTTPS
All transaction from JIRA use Salesforce REST API
Proprietary and Confidential, zAgile, Inc.