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.
Can we use OpenID Connect (OIDC) for single sign-on to our own identity provider IdP to determine which audience-specific pages are shown and their content?
If not OIDC, what protocols are supported?
This is Jesse from the Statuspage support team. Welcome to the community! I took a quick look at some of the documents we have and it appears the only protocol we support is SAML for audience specific pages. We also do support Google Auth but that is in its own little category on Statuspage.
Here is the documentation for setting up SSO with SAML using Okta as the example: https://support.atlassian.com/statuspage/docs/require-saml-for-audience-specific-pages/
Right now, it does not appear that we will be adding support for other protocols at this time. Please let me know if you have other questions or need any clarification.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.