Register this app as a SAML 2.0 service provider on your Shibboleth server from our metadata, release the user attributes and share your identity provider metadata with us.
The values in braces, such as {metadata_url}, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.
-
Register this app as a service provider
Section titled “Register this app as a service provider”On your Shibboleth server, add this app as a SAML 2.0 service provider by loading its metadata from
{metadata_url}. The metadata carries the ACS URL, the entity ID and our signing certificate, so you do not type them in.Paste into Shibboleth:
- SP metadata URL:
{metadata_url}
- SP metadata URL:
-
Check the entity ID and ACS URL
Section titled “Check the entity ID and ACS URL”Confirm that the service provider’s entity ID is
{sp_entity_id}and its ACS URL is{acs_url}. If you configure service providers by hand instead of from metadata, enter these two values.Paste into Shibboleth:
- SP entity ID:
{sp_entity_id} - ACS URL:
{acs_url}
- SP entity ID:
-
Release a persistent name ID
Section titled “Release a persistent name ID”Release a persistent name ID to this service provider, so each user keeps the same identifier over time. If your policy prefers it, release the email address as the name ID instead.
Fixes:
saml_nameid_missing -
Release the user attributes
Section titled “Release the user attributes”Release mail (urn:oid:0.9.2342.19200300.100.1.3), givenName (urn:oid:2.5.4.42) and sn (urn:oid:2.5.4.4) to this service provider. To send groups, also release isMemberOf (urn:oid:1.3.6.1.4.1.5923.1.5.1.1).
Fixes:
saml_email_missing -
Sign responses with SHA-256
Section titled “Sign responses with SHA-256”Make sure Shibboleth signs the SAML response, the assertion or both, and uses SHA-256 (RSA-SHA256) as the signature algorithm.
Fixes:
saml_signature_missing,saml_signature_algorithm_weak -
Share the identity provider metadata
Section titled “Share the identity provider metadata”Add your server’s identity provider metadata to this setup. It is usually published at an address of the form “https://your-host/idp/shibboleth”. Do this again whenever the signing certificate changes, unless this setup reads it from the URL.
-
Test the connection
Section titled “Test the connection”Run a test sign-in in this setup, signing in as a user you assigned to the app.
Optional: add the standby ACS URL
Section titled “Optional: add the standby ACS URL”If our main network ever has an outage, sign-ins can continue through a standby address. Our metadata at {metadata_url} lists it as a second ACS URL, so a server that loads the metadata accepts it. Reload the metadata if you entered the values by hand, check that {standby_acs_url} is listed, then confirm in this setup that you added it.
Paste into Shibboleth:
- SP metadata URL:
{metadata_url} - Standby ACS URL:
{standby_acs_url}
This step is optional. See standby route behavior for what the standby address does during an outage.
Sources
Section titled “Sources”- Profiles for the OASIS Security Assertion Markup Language (SAML) V2.0, read on 2026-10-29
- Metadata for the OASIS Security Assertion Markup Language (SAML) V2.0, read on 2026-10-29