Aloaha Smartlogin exists in two editions. One edition includes the Aloaha Smartcard Connector (CSP) supporting ca. 45 different cards. Those cards can be connected via PC/SC (CCID) or CTAPI (for example eHealth Terminals.
Some customers require a more generic Windows Logon Solution. For example because their card is not one of the 45 supported cards OR they are forced to use their own smartcard middleware.
The second edition supports any smartcard via its middleware (cryptoAPI/CSP) or PKCS #11 module. When using the card via middleware/crypto API the user credentials will be encrypted with the smartcard certificates and stored as a softtoken on the local harddrive or network share. Basically this solution is a 3-factor logon solution since it is require to know the PIN of the Card, the possession of the smartcard AND the existance of the Softtoken.
In case user do not want to use the softtoken based 3-factor solution they can opt to use the PKCS #11 Interface of their middleware. When using the PKCS #11 Library Aloaha will save the user credentials encrypted in a private object ON the card itself!
To store the credentials on the card the user needs to call “PKCS #11 Credentials” from the start menu or PKCS11Credentials.exe from the installation folder (<program files>\wrocklage)
Aloaha Smartlogin PKCS #11 Interface
As a first step the PKCS #11 Library to be used has to be defined! Once that library has been choosen all available token will be listed.
If there is more than one token the user has to select the token to be used in order to save user credentials to the token.
The token removal behavior will be read from the system policy OR from the file Userpass.ini. For details please contact support at firstname.lastname@example.org
To install this edition of Aloaha please download http://www.aloaha.com/download/smartlogin.zip
Please note that a license key is ALWAYS required! Evaluation keys can be requested from email@example.com