Connecting to a Jira Server or Data Center instance
If you're connecting ActionableAgile Analytics to a Jira Server (or DataCenter) instance everything in Load a Jira Board (Legacy Wizard)archived applies, however there are a couple of differences.
Connection differences
Domain | While in Jira Cloud, this is your Atlassian.net based instance. For Jira Server and Data Center instances this is the base url of your Jira instance. This may include a path component. For example - if you access your Jira issues at https://myjira.mycompany.com/jira/browse/ISS-1 then the domain is myjira.mycompany.com/jira |
|---|---|
Username | The username is the username that you use to log into the Jira instance. While in Jira Cloud this is an email address. Depending on your Jira instance this can be an email address OR a username. |
API Token | Instead of using the Atlassian Cloud instance API Tokens, Jira Server instances have their own password. |
Single Sign On
If your Jira instance has Single-Sign-On added onto it - this may change what the details of the above is. Depending on the implementation, Jira may be using a different set of passwords than the ones stored within Jira itself.
We may not be able to support every way your SSO is configured. If you are experiencing difficulty connecting, please reach out to our Customer Support and we will aid you as much as possible. Our Jira ON-Prem Data Loader supports direct integration with Jira’s authentication. Intermediary SSO’s may work but are not always supported.
How are credentials used?
Once the the the above is provided, a base https:// url is formed from the Domain parameter and the Jira instance’s REST API (for example https://myjira.domain.com/rest/api/2/issue/ISS-1 ) is requested. The username and password (API Token) is sent using basic authentication. For more details please see Basic authentication .
The front end service submits the above information to a https service hosted by 55Degrees which in turn makes the request to the Jira instance.