You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi!
Tell me, please, what is the difference between OAuth and Oauth impersonation?
Confluence and jira are now connected via OAuth. For one plugin to work correctly, you need to change the connection to Oauth impersonation.
What can it affect? For example, will someone stop seeing reports or tasks in confluence from jira
Hi @Ступникова Анна Александровна
Here is an explanation of both and their differences as well.
The key is with Oauth with impersonation, the username has to be the same on both instances and when I attempt to access instance B from instance A, instance B checks the user with the same username exists and if yes, uses the token given from instance A to let the user into it.
The user will still only have the same privileges as is configured in instance B.
I will therefore use Oauth without impersonation only if the user has differing usernames between the products so they can login again each time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.