Status page SAML SSO
Put a private status page behind your identity provider, so only people who can sign in to your IdP can see it. You create a reusable SSO connection once, then attach it to as many status pages as you need.
Prerequisites
- A Hyperping Business plan. See pricing for plan details.
- A private status page, or a page you want to make private.
- Admin access to your identity provider.
Pick a connection type
SSO connections come in two types, billed monthly per connection:
| Type | Providers | Price |
|---|---|---|
| Azure AD (Direct SAML) | Microsoft Entra ID / Azure AD | $49/mo |
| Other Providers | Okta, Google, and most SAML or OIDC IdPs | $99/mo |
One connection can protect several status pages, you only pay once per connection.
Step 1: Create the SSO connection
Go to Status PagesSSO Connections to manage your connections.
- Create the connection
Click New Connection. Pick the Provider type, Azure AD or Other Providers, give it a Connection Name like "Corporate SSO", and click Create.
Choosing the provider type for a new SSO connection
Step 2a: Configure an Azure AD connection
The connection card shows the values to copy into an Entra enterprise application, under Use these values in Azure AD Enterprise Application:
| Entra field | Value |
|---|---|
| Identifier (Entity ID) | https://api.hyperping.io/statuspage/saml/sp |
| Reply URL (ACS) | https://api.hyperping.io/v1/auth/sso/statuspage/azure/callback |
- Create the enterprise application
In the Microsoft Entra admin center, create a non-gallery enterprise application, open its Single sign-on → SAML settings, and paste the two values above. The app creation flow is the same as in the Entra ID guide.
- Assign users
Under Users and groups, assign the people or groups who should be able to view the status page.
- Paste the metadata into Hyperping
Copy the App Federation Metadata Url from the SAML Certificates section and paste it into Federation Metadata URL on the connection card. You can also enter the Login URL (SSO URL) and Azure AD Identifier (Issuer) manually instead.
- Save and test
Click Save Configuration, then Test to run a login against your tenant. The card switches to Configured.
The Azure AD connection card with the values to copy and the metadata field
Step 2b: Configure an Other Providers connection
For Okta, Google, and other IdPs, the IdP-side configuration happens in a hosted setup portal rather than on the connection card.
- Fill in the organization details
On the connection card, enter your Organization Name and the Allowed Domains as a comma-separated list, for example
company.com, corp.company.com. - Run the guided setup
Click Open SSO Setup. The portal walks through your specific provider: which app to create, which values to paste, and verifies the connection at the end. Reopen it any time with Manage SSO.
Step 3: Attach the connection to a status page
Go to Status PagesChoose a status pageSettingsPage Access to protect the page.
- Enable SAML SSO on the page
In the page's access settings, turn on the SAML SSO toggle.
- Pick the connection
Select your connection in the SSO Connection dropdown. The dropdown shows each connection's name and allowed domains.
Repeat this on every status page the connection should protect.
How visitors sign in
When someone opens the protected status page, Hyperping sends them to your IdP. After a successful login with an email on an allowed domain, they get a viewer session and land back on the page. No Hyperping account is created, and visitors never appear in your Teammates list.
Troubleshooting
The page says "This connection is not configured yet"
The connection was created but never completed. Open Status Pages → SSO Connections and finish the configuration, then test it from the card.
A visitor signs in but is denied access
Their email domain is not in the connection's allowed domains. Add the domain on the connection, or check that the visitor used their work account at the IdP.
I can't delete a connection
A connection that still protects status pages cannot be deleted. Remove SSO from those pages first, then delete the connection.
Do I need SSO for a simple internal page?
Maybe not. Private status pages also support password protection, email access codes, and Google sign-in, with no per-connection fee.
