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
Next: Root
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.
I'm currently evaluating StatusPage and was wondering if the following is possible:
Requirements:
- Private page only not visible to public
- We use azure SSO for internal domain users
- We also have number of partners not on our domain that will need access to the same page
Is it possible to have both SSO and Atlassian authentication for the same page or how would we go about accomplishing this? Not sure if we would need another Audience specific page to do this and does that mean we have to manage two pages simultaneously?
Thank you
Hey Dragan,
For page-viewers it is not possible to have multiple forms of Authentication for a Private Statuspage subscription. Please see our documentation to learn how you can set up Authentication for Private Pages: https://support.atlassian.com/statuspage/docs/require-saml-for-private-pages/
BR,
Thank you very much. With that being said I am using Trial mode which does not allow multiple pages to be created so i can't test the following scenario; if i was to create another audience-specific page using Atlassian authentication, would incident management and status changes be managed separately on each individual page? Or would we be able to create incidents, send updates, change statuses for Private page and have the same reflected on the audience specific page/group notifications.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For two separate pages all the configurations and incidents will be managed separately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're most welcome! ☺️
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Dragan,
Within your Statuspage organization, you create as many public/private/audience-specific pages within it as you'd like. When logged into manage.statuspage.io you select the page in the top left to open a drop-down to navigate between your organization's pages and add another page.
I will send below a few links on specific topics like page types, and how our SSO works in general.
User level and Different types of pages
Add a New Page
Free Trial
User level - Adding new users
SSO
Require SAML for audience-specific pages
Require SAML for private pages
Basics
Statuspage Basics
Best,
Rafa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much. With that being said I am using Trial mode which does not allow multiple pages to be created so i can't test the following scenario; if i was to create another audience-specific page using Atlassian authentication, would incident management and status changes be managed separately on each individual page? Or would we be able to create incidents, send updates, change statuses for Private page and have the same reflected on the audience specific page/group notifications.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.