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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have seen many discussion around this area, but nothing seems to be concrete.
Issue here is that once customer goes for SSO authentication they would never want their users to keep maintain their passwords with in JIRA, that means white listing REST API while SAML sso in place is not an option.
While i was going through a bit on documentation found https://developer.atlassian.com/server/jira/platform/oauth/
oAuth , JIRA recommended way to authenticate REST Api's however i would like to confirm if this works for all different ways JIRA allows SSO integrations , whether its JIRA Supported (SAML) or non supported ex. through Seraph plugin.
Please share your experience if anyone has gone with oAuth yet.
Hi @Christian Reichert _resolution_ Thanks for message , While passwords are stored at IDP , user name gets created in JIra as user logs in first time to JIRA (through SSO), how does the authentication works if a rest API is called with this user (who doesn't set the password in JIRA) -- is there any ways out here which allows a seemless API call for such users.