​
Overview

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.

​
The Problem: Data Chaos

Each identity provider uses different attribute names for the same user information, creating significant integration complexity: Example: Attribute Naming Chaos
InformationProvider AProvider BProvider C
First NamefirstNamegiven_namefirstname
Last NamelastNamefamily_namesurname
Birth DatedateOfBirthbirthdatedob
National IDpersonalNumberssnnationalNumber
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

​
Our Solution: Normalized Attributes

hConnect maps all provider variations into a attribute set based on OpenID Connect Standard Claims.
AttributeTypeDescription
substringPairwise subject identifier
namestringFull name
given_namestringGiven name
family_namestringFamily name
birthdatestringDate of birth (YYYY-MM-DD)
emailstringEmail address
email_verifiedbooleanWhether the email is verified
phone_numberstringPhone number (E.164)
phone_number_verifiedbooleanWhether the phone number is verified
addressobjectStructured address data
nationalitystringISO 3166-1 alpha-2 country code
updated_atnumberUnix timestamp of last profile update
Examples: See how hConnect transforms provider-specific data into standardized attributes: 
{
  "personalNumber": "198507124567",
  "givenName": "Anders",
  "surname": "Eriksson",
  "name": "Anders Eriksson"
}

​
Data Availability

Not all attributes are available from all providers. The availability depends on each provider’s capabilities and user consent.
If a claim is absent, check missingAttributes in the ID Token or /userinfo. Claims listed there aren’t supported by the provider — handle fallbacks accordingly.

​
Next Steps

Webview Integration

Implement standardized attributes

OIDC UserInfo

Retrieve detailed context and evidence

Provider Reference

Available providers and coverage

Verification Process

Understanding the flow