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
Our project has it;s own token server built on IdentityServer, so it's fully OAuth/ OpenID Connect compliant. Is there any way to authenticate users using that?
I've seen something about using a online directory like Okta, but we have our own (fully standards compliant). It would be very userfriendly if Jira would trust that external identity provider to authenticate customers.
I haven't found anything to that effect but maybe I missed it.. Does anyone have any ideas towards that? Technically it shou;dn't have to be that hard..
Hello, @Gert-Jan van der Kamp
I am pretty sure the SP doesn't actually care what the IdP is, as long as it follows the standards in its responses.
If yours is fully compliant then it should just work. Have you actually tried and found problems?
I suppose you will have to figure out the IdP side of the setup by yourself though, and since it's proprietary – you are unlikely to get help from anywhere...
SP = "Service Provider" in this case Atlassian Access.
IdP = "Identity Provider" in this case your own token server.
If IdP follows the standard, there is not way for a SP to tell what exactly it is talking to. So if you figure out how to configure your IdP to talk to Atlassian Access it will work.
The main issue here is that Access does not support OIDC, only SAML.
If you trust 3rd parties to handle your authentication you can work it via a bridge, see here: https://community.atlassian.com/t5/Atlassian-Access-articles/Log-into-Atlassian-Cloud-using-External-OAuth-OIDC-Provider/ba-p/1731169