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.
Hi Community! Thank you to all who joined our ongoing monthly Atlassian Access demo! We have an engaging group of attendees who asked many great questions. I’ll share a recap of frequently ask...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events