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
Welcome to the Community Wren Sy,
This is a great question, here is the present ( as of Sept 7th 2018) of what is support via SAML:
If your identity provider is in the following table, then follow the link to their instructions for setting up SAML single sign-on. If you can't see your identity provider here, use the instructions provided in the 'Unsupported identity providers' section below.
We don't officially support ADFS, so we recommend using Azure Active Directory instead.
|Bitium||Configuring SAML for Atlassian Cloud|
|Centrify||Centrify's help page|
|Okta||How to Configure SAML 2.0 for Atlassian Cloud|
You'll need to be logged in to OneLogin to see those pages.
For clarity - PingFederate does provide SAML so it will work with Atlassian Access. You'll just need to follow Ping Identity's standard process for creating a SAML 2.0 client / relying party in PingFederate and then follow the instructions in the "unsupported identity providers" section of the document Stephen linked to.
Which options @Kalle Sirkesalo? If you don't see an identity provider you want to use specifically called out in the documentation, you can use the "unsupported" section for generic instructions with Atlassian Access.
Setting it up on the identity provider's side depends on which provider it is. Any provider that can function as a SAML IdP will work. I have pretty good luck searching for "<provider name> SAML relying party" to get instructions for any given provider.