Obo Integration with Jira Data Center / Server (On-Prem
Obo Access to Jira
On your firewall, you need to either (1) whitelist the following IP addresses or (2) allow SSL (https) traffic to your Jira instance from a public IP address.
About Obo's Secure Connection with Jira
The Obo server communicates with your Jira instance using SSL encryption via published Jira API calls. User authentication and privileges are enforced by user-specific API tokens created and managed by Jira.
If you have Jira version 8.14.0 or higher, Obo Apps access Jira using Personal Access Tokens. This allows each Obo user to set up their own secure and private Jira integration in less than a minute - no Jira Admin required. The Personal Access Tokens are managed by Jira and enforce user-level project permissions.
If your Jira version is pre-8.14, the Obo server uses OAuth authentication to connect with Jira. A Jira user with Jira admin privileges must perform the initial Obo Jira setup, which creates the OAuth relationship between the Obo and Jira (takes less than 5 minutes). Subsequent Obo users set up their own secure and private Jira integration using OAuth API tokens in less than a minute. The OAuth API tokens are managed by Jira and enforce user-level project permissions.
Obo supports SAML2.0 Single Sign-On.
Obo hosts its SaaS applications in AWS and enforces a strict security framework.
Obo is an approved Atlassian Vendor and its apps are in the Atlassian Marketplace.
If you have any questions contact firstname.lastname@example.org.