nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Supporting JIRA REST API support if users are using SSO

Gaurav Nigam

Hi,
We (Workboard) provide seamless Jira integration with REST API with basic authentication and it works absolutely fine for all our customers. But with our enterprise customer tier, our REST API is failing as they use the SSO login. Our REST APIs are resulting in 403 error.

We need to know what should we do to support this?

We have also gone through this link with no luck.

https://community.atlassian.com/t5/Confluence-questions/REST-API-behind-SAML-with-3-Legged-OAuth/qaq-p/585795

Also, If the user sets a password in his Jira account and then we use this username and password, will that work?

Accepted answers

All comments

Bruno Vincent

Hi @Gaurav Nigam,

It really depends on your SSO solution. It should have configuration options to exclude REST URLs or include only specific user agents.

Which SSO solution/add-on do you actually use?

Gaurav Nigam

Thank you, Bruno!

This enterprise customer uses their own IDP. So changing at their SSO level, it would be a tedious task. Though we have requested them to explore that.

Is there any other option like supporting both username/password and SSO at the same time?

Lars Olav Velle

What IDP the customer is using matters less. What matters is what add-on you are using.

I cannot speak for others, but with Kantega Single. Sign-on you can have both Kerberos and basic auth to REST at the same time. You can also limit who is offered SSO by IP white/blacklisting.

If you have any questions feel free to reach out to our support team at sso@kantega.no

Cheers,

Lars, Kantega Single Sign-on

Bruno Vincent

Hi @Gaurav Nigam

So, my understanding here is that this is a SAML based SSO solution. But which one is this? If we're talking about Jira Server then this must be an add-on. If we're talking about Jira Data Center, then this might be Atlassian's native solution. Or maybe we're talking about Jira Cloud here?