Even though the focus of Aloaha is put on Smart Cards we do have APIs to read 2W, 3W, i2c Memory Cards such as the famous SLE4428, SLE4442, telephone cards, german KVK (Krankenversicherungskarte), Kinko, Student Card, etc.

The API to read such cards is included in the Aloaha Cardconnector, Credential Provider and Smartlogon. No license is required to just read them!

Code Sample:

dim cr
dim reader

set cr = createobject(“AloahaSync.SyncAPI”)
   reader = cr.ReaderNamesCSV
   reader=split(reader,”,”)(0)

   if reader<>”" then
      If cr.Connect(reader) = True Then
         msgbox cr.hexdump(cr.raw_content)
      end if
   end if
set cr = nothing

For german KVK Cards please also try API: cr.KVK_Content

Please note that for the new German Health Card (eGK / Gesundheitskarte) you should follow the instructions on: http://blog.aloaha.com/2012/03/21/deutsche-gesundheitskarte-auslesen/

KVK Specification

Please make sure that when you are using an HID/Omnikey Reader that you install the Sync API additionally to the reader driver. When using SCM Microsystems Reader you need to make sure that the MCARD API has been installed additionally to the reader driver!

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 info@aloaha.com

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 info@aloaha.com

Aloaha accesses per default the connected Smart Card Reader via the Windows PC/SC or CCID driver. In some cases it might be required to use the reader via CT-API. For example in cases that no PC/SC or CCID driver exists. That is the case for most health terminals used in the german health system.

To be able to use CT-API it is required that a recent version of the Aloaha Smartcard Connector is installed. If you find the file AloahaCSPPlugin.exe in <common files>\Aloaha your Version is recent enough to be switched to CT-API.

To activate CT-API there have to be entries in the file CTAPIINI.ini in <program files>\wrocklage and entries in the registry.

CTAPIINI.ini:

[Settings]
activated=1
CTAPI=c:\windows\system32\ct8751.dll
[HID OMNIKEY 8751 e-Health LAN]
port=1
Units=01,02,03,04,40,50

Please note the the settings section is required. The rest Aloaha will try to fill in automatically.

Once the above seetings are done you you re-logged on into your machine you will see your CT-API eHealth Terminal in the Aloaha Systray as shown below:

Aloaha System Tray with e-Health Terminal

Even though any CTAPI Reader should work currently ONLY the ORGA 6041 eGK and OMNIKEY 8751 eHealth terminals have been accredited to work perfectly with Aloaha. More will follow on request!

Windows Logon with e-Health Terminal

Obviously the Aloaha Smartlogon does support Windows Logon via CTAPI based Smartcard Reader. That means that it is possible to use a HID 8751 or Orga 6041 eHealth Terminal to logon to with the german HBA (Health Professional Card).

Per default the e-Health Terminal is NOT connected to the Windows Logon Credentials Provider. To activate that you need to create the following entry in our CTAPIini.ini in your installation folder:

[Settings]
CTAPIAsSystem=1

After you create the key and set your credentials via Aloaha GUI you can logon via the Aloaha Tile as shown below:

Aloaha Windows Logon

You can download the Aloaha Middleware/Credential Provider from http://www.aloaha.com/download/credentialprovider.zip

Please make sure to request an evaluation key from info@aloaha.com

German cutomer should also read: http://blog.aloaha.com/2012/01/03/wie-richte-ich-mein-ehealth-terminal-ein-um-mich-mit-meinem-hba-oder-smc-karte-an-windows-anzumelden/

The Aloaha Crypto Card is now also available as Contactless Card. Please contact info@aloaha.com for further information.

Details for the Crypto Card can be found on: http://www.aloaha.com/smartcard-software-en/aloaha-crypto-card.php

Aloaha Smartlogin is the ideal solution logon with your smartcard to Windows XP or 7.

Plain USB Memory Sticks are supported for people without smartcards. Logon with Plain USB Memory Sticks is freeware for private use!

Aloaha Smartlogin 4 USB Memory can be downloaded from http://www.aloaha.com/download/smartlogin.zip

A short usage video can be found on:

All Aloaha products are now natively supporting the OpenPGP Cards (v2.0) and GPF Crypto Stick

To use your OpenPGP Card in Windows does not require any non Aloaha Software anymore!

Many thanks to Achim & Jan!

More on http://www.privacyfoundation.de/aktuelles/detail/zurueck/akutelles/artikel/crypto-stick-in-kommerzieller-software-integriert/