# September 24, 2026

Sign SAML authentication requests for organization and status dashboard single sign-on.

Source: https://statusdashboard.com/docs/releases/2026-09-24

SAML single sign-on providers can now **sign authentication requests**. Some identity providers only accept sign-in requests they can verify, and this lets StatusDashboard meet that requirement for both organization SSO and status dashboard SSO.

Signing is off for every provider until an admin turns it on, so existing SSO setups keep working unchanged. For the full setup steps, see [SAML for organization SSO](/docs/security/sso/saml) and [SAML for status dashboard SSO](/docs/status-dashboards/sso/saml).

***

## Added
* **Sign authentication requests** on the SAML provider in the **Single Sign-On** page, and on the **Single Sign-On** tab of a status dashboard. The control is not shown for OIDC providers.
* **Download signing certificate**, available once signing is on, so you can install it in your identity provider. Organization SSO and status dashboard SSO use separate certificates.
* **Certificate rotation:** each certificate is valid for 10 years, and a new one is published about once a year. The previous certificate stays valid and the public key does not change, so you can replace it in your identity provider on your own schedule.
* **API:** a `signAuthnRequests` field on SAML providers returned by [Get provider](/docs/api/security/sso/get), [List providers](/docs/api/security/sso/list), and [Get dashboard SSO](/docs/api/status-dashboards/dashboards/sso/get). New endpoints to toggle signing and download the certificate for [organizations](/docs/api/security/sso/authn-signing) and [status dashboards](/docs/api/status-dashboards/dashboards/sso/authn-signing). See [Download signing certificate](/docs/api/security/sso/signing-certificate) and the [dashboard equivalent](/docs/api/status-dashboards/dashboards/sso/signing-certificate).

## Changed
* **Existing providers:** signing stays off until you enable it. Uploading new identity provider metadata does not turn signing off.
* **Create and update requests:** the [Create](/docs/api/security/sso/create) and [Update](/docs/api/security/sso/update) provider bodies are unchanged and do not accept a signing flag. Use the toggle endpoint instead.

## Security
* **Signed requests:** with signing on, your identity provider can require signed authentication requests and reject any it cannot verify. Install the certificate and test with one user before you turn on that requirement. Keep [Break Glass Access](/docs/security/sso/break-glass) for at least one admin first if your admins sign in only through SSO.
