onelogin saml invalid nameid format error

Fix OneLogin SAML invalid NameID format error

TL;DR

Invalid NameID format means the SAML response carries a NameID format the app does not accept, or the value is empty. Open the OneLogin app connector and set the NameID format to what the app expects, usually email address. Then confirm the mapped user field actually has a value for the failing user.

The error

SAML Error: Invalid NameID format
The NameID format in the assertion is not accepted by the service provider.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=onelogin saml invalid nameid format error"

Fix it

Step 1: Confirm what NameID format the app expects

Check the app's SAML docs or its error detail; most expect urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.

Expected: You know the exact format string the app wants.

Step 2: Set the NameID format in OneLogin

OneLogin Admin -> Apps -> [app] -> SSO -> set the Name ID format to the expected value and save.

Expected: The connector shows the correct format and saves cleanly.

Step 3: Verify the mapped user field is populated

Check that the field mapped to NameID (usually email) has a value for the failing user in OneLogin.

Expected: The user has a non-empty value in the mapped field.

Step 4: Test with the SAML tracer view

Log in again and inspect the assertion; the NameID element should carry the right Format attribute and a value.

Expected: The assertion shows the expected format and a populated NameID.

Step 5: Re-test login end to end

Start a fresh SP-initiated login for the affected user.

Expected: Login succeeds with no NameID error.

When this applies

• OneLogin SAML logins fail with invalid NameID format
• Some users fail while others with the same app succeed
• You just changed the NameID mapping in OneLogin

When it doesn't

• All SAML logins fail including signature checks (check the certificate first)
• The NameID is right but attributes are wrong (that is attribute mapping)
• You use OneLogin OIDC rather than SAML

Compatibility

OneLogin SAML app connectors. Applies to the standard OneLogin SAML Test and vendor connectors.

Variant phrasings

onelogin saml nameid format invalid

Same error. The fix is always format plus a populated mapped value.

nameid format not supported onelogin

The app rejects the format OneLogin sends. Match it to the app's documented expectation.

empty nameid onelogin saml error

When the mapped field is blank for a user, the assertion carries an empty NameID and the app rejects it as invalid.

Why it happens

The NameID is the user identifier inside the SAML assertion, and it carries a format label telling the app how to read it. If OneLogin sends persistent but the app expects emailAddress, or sends an empty value because the mapped field is blank, the app rejects the assertion. It is a contract mismatch between the two sides, not a crypto problem.

Edge cases

• Users without an email in OneLogin fail while everyone else passes; backfill the field
• Changing the NameID format can break already-linked accounts that were matched on the old value
• Test connectors default to unspecified format; vendor apps almost never accept that

If it still fails

• Capture the exact timestamp, the failing username, and the full error from the IdP system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• Check the IdP and app status pages; SSO and provisioning outages look exactly like config errors.
• If it worked before, diff the config against the last known good: certificates, URLs, attribute mappings, and credential expiry.
• Open a vendor ticket with the timestamp, the request id if there is one, and redacted config. Never send secrets or private keys.

Prevention

• Track certificate and credential expiry with alerts, not memory.
• Run a synthetic login per SSO app daily so breakage pages you, not a user.
• Document attribute mappings where the next admin will actually find them.
• Test provisioning with a single user before bulk changes.
• Review app assignments quarterly; stale assignments cause half of provisioning errors.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_e-oY9vLIdJouzlqQz72tBA

Resolved from the public thread: https://vectle.com/posts/pst_e-oY9vLIdJouzlqQz72tBA

Thread query: onelogin saml invalid nameid format error

TL;DR: Invalid NameID format means the SAML response carries a NameID format the app does not accept, or the value is empty. Open the OneLogin app connector and set the NameID format to what the app expects, usually email address. Then confirm the mapped user field actually has a value for the failing user.