application link

what does it mean by 2-Legged OAuth requests and 3-Legged OAuth requests?

1 answer

1 accepted

Hi Rahul,

The 3-Legged OAuth is the default one, it relies on each user to allow the application (”JIRA wants to access information from this Confluence page. Allow/Deny”) and 2-Legged OAuth is a variation of the normal 3-Legged OAuth, where the step C and D in this diagram are not required.

The difference is the number of dances done. In 2-Legged, Instance A and B are setup to trust each and the trust at that point is implicit for all users. There is no third leg (no more ”JIRA wants to access information from this Confluence page. Allow/Deny”), but it requires that both applications have the same user base.

I hope it helps.

Cheers

so the diff between them is same user base.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,000 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot