How the concept is used
An identity can be as simple as an internal customer number, or it can depend on checked information from an electronic ID. Context matters: an email address may identify an account without proving the person’s legal name or age. A verified identity can support more sensitive actions. A business should therefore describe which attributes it knows, who checked them and the purpose for which each attribute is used.
A practical example
Imagine that Maya opens a shop account with her email address. The shop can recognise that account on a later visit, but it does not yet know whether she meets the minimum age for a particular product. A separate age check can provide the missing answer without making every other identity attribute available. Account recognition, a contact address and proof of age solve different problems and should remain distinct in the design.
Important distinctions
Identification, authentication and authorisation describe different stages. Identification establishes which user is being considered; authentication checks the user’s evidence for access; authorisation decides what that user may do. None automatically means that every statement about the person is verified. For a business, asking a narrow question about an age threshold can be more appropriate than requesting a complete identity without a defined reason.
Sources
- W3C: Decentralized Identifiers (DIDs) v1.0 Checked
- NIST: NIST SP 800-63A-4: Identity Proofing and Enrollment Checked
- NIST: NIST SP 800-63B-4: Authentication and Authenticator Management Checked
These explanations were prepared with AI assistance and draw on the sources listed.