REST API behind SAML with 3-Legged OAuth

Andy Kim May 10, 2017

We have 3-legged OAuth working to access the REST API for Confluence Server / Cloud. Unfortunately for our clients using SAML, when we issue the API call to fetch the request token (see https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-oauth-authentication), our servers receive a 302 redirect to authenticate via SAML.

What is the recommended way to handle REST API calls behind SAML? How unique are the flows depending on SAML provider?

Thanks and apologies in advance as I'm not very familiar with SAML.

1 answer

0 votes
Moga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 30, 2017

Hi Andy,

I hope that this helps!

Cheers!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events