Authentication options on StatusPage

[Priyadarshini R Kolwalkar]

Hi, 

  As a current user of StatusPage, we need to start using SAML authentication. Is there a workaround to login incase on an IDP outage? Could I setup one "master" user which can login via username/password instead?

  If not, what would one recommend in such a situation?

Thanks,

Priya

[Abraham · Accepted solution]

Hey @Priyadarshini R Kolwalkar

Thanks for reaching out about this! 

Before configuring SAML single sign-on, you can create an Atlassian account that you can use to access your organization even if SAML has been mis-configured or down.

This account:

• must not use an email address from a domain you have verified for this organization. This ensures that the account will not redirect to SAML single sign-on when you log in.
• must be given organization admin access.

You can read more about this here.

Cheers! 

[Priyadarshini R Kolwalkar]

This is helpful, thank you for your response @Abraham

[Zach · Accepted solution]

Hey Priya, 

While legacy Statuspage authentication does not allow for a single user to remain outside of the enforced SSO restriction, it is possible within Atlassian Access. 

In the SAML setup guide for Atlassian Access there is a section titled "Before you begin" that contains some useful information on this exact topic -

Before configuring SAML single sign-on, create an Atlassian account that you can use to access your organization even if SAML has been mis-configured. This account:

• must not use an email address from a domain you have verified for this organization. This ensures that the account will not redirect to SAML single sign-on when you log in.
• must be given organization admin access.

So while you could always add a generic gmail address for accessing in case of emergencies, I'd suggest using a different domain that might be owned by your company that isn't claimed so that it can authenticate using Atlassian account credentials. 

[Priyadarshini R Kolwalkar]

This is helpful, thank you for your response @Zach