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
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
I am digging the documentation to understand the capabilities of OAuth applications / integrations.
I do understand that you can integrate with Atlassian products with OAuth apps with authorization code flow, which means by its definition that you need to have user-context available (interactive sign-in). For instance, user does a sign-in on a web page which is redirecting the user to get the auth code and proper access token.
But how are integrations designed which support a system-to-system process? Processes where user context is not available? PAT is definitely not be the preferred option from an enterprise perspective as it is using basic auth protocol, which you want to avoid actually.
What is the best-practice for system-to-system communication with modern auth protocols? I am looking for sth. like a client-credential flow which supports non-interactive processes.