DIGIPASS Authentication for TAM - Vasco

10 DIGIPASS Authentication for TAM
DIGIPASS Authentication for TAM
5 Token Repository
5.1 STORING VASCO DIGIPASS TOKEN INFORMATION
As stated above, the DIGIPASS CDAS uses the TAM LDAP Directory as its repository to
store token information. In the current release both IBM LDAP and SunOne LDAP are
supported. The token information is stored in an object that is located in a sub tree under
the user with whom the token is associated.
The following screen dump shows such an entry.
This screen dump shows that the token with serial number 0097123456 is associated
with the TAM user with DN (Distinguished Name) cn=Allowed1, o=sov, c=be. The
CDAS makes absolutely no assumptions about the format of the DN, as long as it is
accepted by TAM. The token information is stored as an instance of the Object Class
sitVASCOToken. The object is created under the secAuthority=Default entry created
by TAM.
A token entry basically contains the following information:
sitVASCO Type of the token (e.g. ResponseOnly)
sitVASCOApplName Application using the token
sitVASCOBlob The token details, aka. BLOB (contains e.g. current valid pincode)
sitVASCODpFlags Token flag (internal use)
sitVASCOSerialNr Token serial number (to physically associate a token with a
user)
sitVASCOMode Mode of operation (optional)
sitVASCOType Type of token (optional)