The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

application link

rahuldanwade
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 1, 2014

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

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Tiago Comasseto
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 1, 2014

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

rahuldanwade
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 2, 2014

so the diff between them is same user base.