Applicable Product:
- Peoplefluent Learning
Applicable Release:
- N/A iPaaS Enabled Customers
Summary:
When configuring Single Sign-On (SSO) between your Identity Provider (IdP) and iPaaS, one of the most important settings is the NameID value transmitted within the SAML assertion.
The NameID acts as the user's unique identifier during the authentication process. iPaaS uses this value to locate and authenticate the appropriate user account. If the NameID is missing or mapped incorrectly, users may be unable to access their PeopleFluent applications even if authentication succeeds with the Identity Provider.
What Is a NameID?
The NameID is a standard SAML attribute that uniquely identifies a user.
When a user signs in through their Identity Provider, a SAML assertion is sent to iPaaS containing user information. The NameID is included in that assertion and iPaaS uses it to determine which account to authenticate.
How iPaaS Uses the NameID
During the login process:
- The user authenticates through the Identity Provider.
- The Identity Provider generates a SAML assertion.
- iPaaS receives the SAML assertion.
- iPaaS reads the NameID value.
- iPaaS attempts to locate a matching user record.
- If a matching account is found, access is granted.
If a matching account cannot be found, authentication will fail.
Recommended NameID Values
The NameID should contain a value that:
- Uniquely identifies the user
- Remains consistent over time
- Exists within iPaaS
Common examples include:
- Employee ID
- HRIS Identifier
- External ID
- Corporate Username
While email addresses can sometimes be used, organizations should be aware that email addresses may change over time and can create account matching issues if not managed carefully.
Common Configuration Issues
Missing NameID
If the Identity Provider is not sending a NameID value, iPaaS cannot identify the user.
Potential Symptoms
- Login failures
- Authentication loops
- Users redirected back to the login page
- SSO validation errors during implementation testing
Incorrect NameID Mapping
The NameID may exist but be mapped to the wrong value.
For example:
| Expected Value | Actual Value Sent |
|---|---|
| Employee ID | Email Address |
| External ID | Username |
| Username | Email Address |
If the value being sent does not match the value stored within iPaaS, authentication may fail.
Multiple User Identifiers
Many Identity Providers allow multiple user attributes to be sent during authentication.
Although additional attributes may be included, it is important to understand which value is being sent specifically as the NameID.
The NameID should be documented as part of your SSO configuration to avoid future issues.
Validating Your Configuration
Before enabling SSO for production users, verify the following:
- A NameID value is being sent
- The NameID matches the expected identifier within iPaaS
- Test users can successfully authenticate
- Both administrator and standard user accounts have been tested
- Authentication succeeds in a private/incognito browser session
Best Practices
- Use a stable identifier whenever possible.
- Avoid identifiers that may change frequently.
- Document NameID mappings during implementation.
- Validate NameID configuration during all Identity Provider changes.
- Re-test authentication after any SAML configuration updates.
When to Contact Support
Contact Support if:
- The NameID appears correct but authentication still fails.
- You are unsure which identifier should be used.
- Authentication worked previously and suddenly stopped after a configuration change.
- You need assistance reviewing a SAML assertion or troubleshooting SSO behavior.