Source
API, monitoring as code & team administration — found from sitemap — Atlassian Statuspage
Checked for Atlassian Statuspage on 1 Nov 2026
- Page
- https://support.atlassian.com/opsgenie/docs/configure-saml-based-sso/
- Checked
- 1 Nov 2026, 10:50 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:cf50241fc38cf42e6e5c2ceaf063e0123143f70adce37eaec7a8192a9da0df1d
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SAML SSO supported Report an error
“Opsgenie acts as the service provider and supports SAML 2.0 based Single Sign-On to authenticate users through different identity providers.”
-
SSO any identity provider Report an error
“You can enable our Single Sign-On solution using any identity provider, even ones that are currently not one of our partners.”
-
Slo supported Report an error
“If your identity provider supports Single Logout (SLO),”
-
SSO endpoint URL Report an error
“https://app.opsgenie.com/auth/saml?id=<saml_id> where <saml_id> is unique per Opsgenie account.”
-
SAML settings path Report an error
“From your Opsgenie, go to Settings → Login and SSO. Select SAML as your identity provider.”
-
SAML name id format Report an error
“Name ID format is expected to be: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress”
-
SAML encryption cert restriction Report an error
“An encryption certificate for claims should not be used.”
-
SAML protocol binding Report an error
“ProtocolBinding: urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST”
-
SAML SSO configuration doc partners Report an error
“Learn more about configuring SSO for Opsgenie to take a look at identity provider partners, the requirements to enable Single Sign-On for authentication, and how to configure and use Single Sign-On solution.”