The Token is the central concept of this endpoint. It represents a physical or virtual entity or device that supports a user in the authentication process. Examples are SecurId tokens, phone numbers or registered mobile app instances. A token consists of a unique tokenId
and a configurable set of attributes. The actual set of attributes depends on the persistency implementation used.
Currently, IAM supports three different kinds of persistency implementations (aka repositories):
- token-based: based on the IAM token data model (TokenDataProvider)
- credential-based: based on the IAM credential bean model (CredentialPersister)
- custom implementation: custom implementations of the GenericTokenRepository interface may be provided (see bottom of page)