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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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