Aloaha Credential Provider

The new Aloaha Credential Provider represents one of the most dramatic changes in the Windows Vista/7 logon screen, making it much easier to implement new user authentication scenarios that are suppor
Download

Aloaha Credential Provider Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Trial
  • Publisher Name:
  • Wrocklage Intermedia GmbH
  • Publisher web site:
  • http://www.aloaha.com
  • Operating Systems:
  • Windows 2K / XP / Vista / 7
  • File Size:
  • 11.5 MB

Aloaha Credential Provider Tags


Aloaha Credential Provider Description

Smartcard Logon to Windows Machines - without requirement of domain controler The new Aloaha Credential Provider represents one of the most dramatic changes in the Windows Vista/7 logon screen, making it much easier to implement new user authentication scenarios that are supported by the OS. To be able to logon via Smartcard to a windows machine requires usually the machine being a member of a domain. With the Aloaha Credential Provider that is not required! The logon screen is the first thing users see when they turn on the computer. The function of the Aloaha Credential Provider is to supply the OS with logon credentials. The logon credentials are saved encrypted on the local hard drive. In case the user uses the Aloaha Crypto Card the credentials are additionally saved encrypted on the card itself. When the user now types in Username, Domain\Username and Card Pin the Credential Provider will decrypt the locally saved credentials and pass them to the OS. Please note that you can leave the fields empty. In that case Aloaha will use the most suitable credentials found on the smardcard. To save an encrypted password just type into the 2nd field setpass: followed by the password. For example setpass:letmein. Aloaha will then encrypt the password with the certificate of the smartcard and save it locally. In case the Aloaha Cryptocard is used the credentials will also be saved encrypted on the card itself. There is also a mechanism to synchronise the encrypted credentials across the network. Just create a registry key HKEY_LOCAL_MACHINE\SOFTWARE\Aloaha\CSP\RemoteUserPass pointing to a file in the network or an URL. For example the content could be \\192.168.0.127\download\UserPass.ini or http://192.168.0.127/download/UserPass.ini. Such an entry would mean that in case Aloaha does not find locally encrypted credentials it will look for them in the file specified in RemoteUserPass.


Aloaha Credential Provider Related Software