Two terms often used interchangeably in our community are Credential and Token. But they are not the same since what each is able to assert online is not the same. This blog post delves a bit deeper into this topic and the value provided by a Token to both individuals and relying parties.
All too often, the natural inclination of those who build high value online services is to demand identity up-front as a precursor to service delivery. The justification is that doing this 'account setup' upfront makes the conversion to actual identity-driven service delivery easier (for the Relying Party).
The classic example of the failure case for this thinking was the first iteration of HealthCare.gov as documented in the UX analysis done by the Nielson Norman Group. That has since been addressed, but it provides a clear example of the value of separating the need for 'Sameness' (provided by a Token) from the need for 'Identity' (provided by a Credential).
- Token: Something that an individual possesses and controls that is used to authenticate the individual and is controlled through one or more of the traditional authentication factors (something you know, have, or are)
- Tokens answer the question 'Are you the same person I encountered before?' (without leaking the identity of the person)
- Credential: An object or data structure that authoritatively binds an identity to a token possessed and controlled by an individual
- Credentials answer the question 'Who are you?'
Separating the two and having a clear process to move from the usage of a Token to a Credential provides benefits to both individuals and relying parties:
|Benefits to the Individual||Benefits to the Relying Party|
Question: Is it possible to ensure that the same person has maintained control of a token without a strong process for the initial binding of the person to the token?
- Balancing Identity Assurance and User Enrollment UX
- NIST SP-800-63-1 Multi-Token Assurance Level Matrix
Did you find this interesting? Don't miss any new posts. Sign up to automatically receive them now!
This blog post first appeared on Anil John | Blog (https://blog.aniljohn.com). The opinions expressed here are my own and do not represent my employer’s view in any way.