Authoritative Source
Identity attributes come from source-controlled integrations where confirmed.
Connect national identity to enterprise identity-assurance journeys.
Connect national identity to enterprise identity-assurance journeys.
Identity attributes come from source-controlled integrations where confirmed.
SSO / ShareInfo patterns are separated from verification evidence.
Source → CheckID → RP
↗Citizen → VNeID/eID/CCCD → authorized source/service → CheckID → relying party
The publication distinguishes citizen/user, relying party, CheckID/Mobile-ID, identity provider and authoritative source. CheckID is not represented as the owner of population data when the source authority is a government body.
SSO/VNeID authentication establishes a session/assertion according to the integration; it does not automatically mean every identity attribute has been shared or verified.
ShareInfo/attribute sharing requires purpose, authorization/consent, scope and source provenance according to contract. SSO and ShareInfo are not synonyms.
Document/chip trust and authoritative-source checking are separate evidence paths. NFC/chip reading is not automatically equivalent to online government-source verification.
Access to authoritative sources must be purpose-, authority- and service-scope controlled. Public documentation does not use “unrestricted/direct population database access” language.
Relying parties need correlation among identity process, source/method, attributes/result and evidence through fields actually exposed by the implementation.
Navigate directly to detailed capability and service publications.