Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Authenticate users using my own OpenID Connect (OAuth) server?


Hi all, 

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.. 

1 answer

1 accepted

1 vote
Answer accepted

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...

Hi sorry for late reply I got distracted. What is SP exactly and where could I find that setting? Thanks in advance, GJ

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:

Like Steffen Opel _Utoolity_ likes this

That's a great article thx. It does seem however this is not supported out of the box so that's less good news. I may have to park this for now. Guess having people enter their email for their first issue good enough for now. Thanks! 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events