hConnect solves the fragmentation problem of identity providers by standardizing user attributes across all eID providers. No matter which provider your users choose, you receive consistent, predictable data formats.
Each identity provider uses different attribute names for the same user information, creating significant integration complexity:Example: Attribute Naming Chaos
Information
Provider A
Provider B
Provider C
First Name
firstName
given_name
firstname
Last Name
lastName
family_name
surname
Birth Date
dateOfBirth
birthdate
dob
National ID
personalNumber
ssn
nationalNumber
Without standardization, you would need to:
Write custom mapping logic for each provider
Maintain provider-specific code branches
Handle different date formats and data types
Update your code when providers change their schemas
hConnect maps all provider variations into a attribute set based on OpenID Connect Standard Claims.These are standard OpenID Connect claims representing the user’s identity.
Personal attributes are returned under /userinfo.user.*. The ID Token contains no PII; it carries only technical claims (for example: sub, acr, hopae_loa).
Examples: Provider data vs. normalized /userinfo.user:
