application link

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

1 answer

1 accepted

0 votes
Accepted answer

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 Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,950 views 19 22
Read article

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