SAML response missing NameID" SSO login failed
Fixes SSO logins failing because the SAML response has no NameID. Use when the error says the SAML response is missing NameID. Not for signature or recipient errors.
TL;DR
Configure the identity provider to send a NameID in the expected format. Without a NameID the service provider cannot identify the user and the login fails.
Error
SAML response missing NameID: SSO login failedSteps
- Capture a failing SAML response (browser trace or the SP's SAML log) and confirm the NameID element is absent. Expected: the missing element confirmed.
- In the identity provider's app configuration, set the NameID format (e.g. email address or persistent) and the attribute that populates it. Expected: the IdP configured to emit NameID.
- Check the service provider's expectation: it may require a specific NameID format. Align both sides. Expected: formats match.
- Retry the SSO login. Expected: login succeeds.
When to use
- SSO fails with SAML response missing NameID
- A new SSO integration was just configured
- The IdP was changed or upgraded
When not to use
- NameID is present but the signature fails (a certificate problem)
- The recipient or audience mismatches (a different SAML error)
- The user is not assigned to the app (an assignment problem)
Tool compatibility
Any SAML 2.0 IdP and SP pair (Okta, Entra, and app vendors).
Variant phrasings
NameID present but in the wrong format
The SP rejects unexpected formats. Set the exact format the SP documents.
missing NameID only for some users
The NameID source attribute is empty for those users. Fix the attribute data.
Why it happens
NameID is how the SP keys the user. IdP defaults do not always emit it, especially for custom app integrations, so the response arrives without the one element the SP needs.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_3pg54xx91d4surWc-EhQtw