Summary

When Jira Align is integrated with an SSO-enabled Jira instance, a common requirement is for the Connector to bypass SSO when it connects to Jira.

This is because the Connector is not designed to handle SSO. It simply connects with the credentials it has been configured with and cannot respond to an Authentication challenge from an Identity Provider.

Solution

There are a few possible solutions:

1 - Jira Server / Datacenter offers a “nosso” query string parameter that can be used to bypass sso. Testing has shown that this works when appending to the Connector configuration’s Jira Link URL:

2 - Add the Jira Align outbound IP address to the SSO application’s bypass list

• For Jira Align On-Premise, the customer must determine their Jira Align host’s IP address

• For Jira Align Cloud, there are two outbound IP addresses. Support can determine the appropriate IP addresses from https://hello.atlassian.net/wiki/spaces/JALN/pages/583408551 and provide these to the customer

3 - Add the Jira API URLs required by the Connector to the SSO application’s bypass list

/rest/auth/*
/rest/api/2/*
/rest/agile/1.0/*
/rest/greenhopper/1.0/*

If the Connector is configured to use OAuth 1.0 to authenticate, the following URL must also be included:

/plugins/servlet/oauth/*

Each of these solutions should allow the Connector to bypass SSO and log into Jira directly with its stored credentials.