Authoritative Source
Identity attributes come from source-controlled integrations where confirmed.
Separate federated sign-in, attribute sharing and policy-bound consent evidence.
Separate federated sign-in, attribute sharing and policy-bound consent evidence.
Identity attributes come from source-controlled integrations where confirmed.
SSO / ShareInfo patterns are separated from verification evidence.
Source → CheckID → RP
↗Source → Scope → Evidence → Limitation
SSO establishes an authentication/session context using the integrated mechanism.
ShareInfo is an authorized attribute-sharing step when the source/service permits it.
Consent/authorization is tied to purpose and relying party, not merely to the fact that a user signed in.
A relying party should request only attributes needed for purpose rather than a complete profile by default.
Where sourced, transaction/session/process identifiers make the attribute-sharing context auditable.
Raw tokens/credentials and sensitive data payloads are not exposed on the public site.