Frequently Asked Questions
We've compiled a list of answers to common questions. Please do not hesitate to send us questions or suggestions.
The CodeB Credential Provider 2 supports every Windows edition starting from Windows 8 and onward. In case you have older machines you might want to contact us for Aloaha Smartlogin.
You can still download the old legacy Aloaha Smart Login from: https://www.win-logon.com/aloaha_smart_login_home/
Out of the box, the CodeB Credential Provider is compatible with plain USB memory sticks, NFC cards based on MIFARE and DESFIRE, X.509 PKI Smart Cards, software certificates, TOTP codes, and Mobile OpenID Connect. To inquire about integrating a specific security token, please contact our support team.
MIFARE and DESFIRE cards are the most common NFC tokens used by our customers. You can also use other contactless cards, like your companies ID Badge, Credit Cards, Bus Tickets, or Student Cards. Alternatively, you can turn your phone into an NFC token by installing the CodeB Authenticator app.
HID Prox Cards are supported. Obviously you need to have the right reader as HID Prox Cards use only 125 kHZ
They utilize Time-based OTPs in accordance with RFC 6238. TOTPs can either be transmitted via SMS or produced by applications such as the CodeB Authenticator.
In a typical Windows setup, it’s essential to deactivate the “Microsoft Password Provider” to prevent password logon. However, if your system’s manufacturer has integrated a custom credential provider, it might be necessary to disable that specific provider as well. Always ensure you’re deactivating the correct providers to maintain the security and functionality of your system.
When employing the Remote Desktop Connection tool to gain access to a distant computer, it’s entirely possible to use smartcards within that remote environment, provided they are connected to the client machine. To achieve this, one must configure the remote connection settings appropriately, ensuring that smartcards from the client computer are relayed through to the distant system.
However, there’s a notable exception: if a smartcard is physically attached to the remote computer, its use within the remote session becomes restricted. This limitation arises from the session management protocols of the operating system, which, for security considerations, inhibit access to devices directly connected.
For scenarios where there’s a pressing need to access a smartcard directly linked to the remote computer, perhaps for remote support purposes, alternative remote computing solutions might be more suitable. These tools can circumvent the session management restrictions, granting the necessary access.
To ensure that 2-factor-authentication is active even when operating in safe mode, a modification to your Windows registry is required. Specifically, navigate to the registry path:
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion\Authentication\Credential Providers”
Within this location, you should create a new REG_DWORD entry named “ProhibitFallbacks”.
We strive for complete customer satisfaction. To ensure this, we provide evaluation keys and dedicated support throughout the trial period. We believe in our product and want you to be fully content before making a purchase. Consequently, the need for refunds is exceptionally rare.
Of course we have a partner program. Read more on: https://www.win-logon.com/partner/
Absolutely, the Aloaha Smart Login remains available and continues to be maintained. However, we highly recommend transitioning to the CodeB Credential Provider V2. Not only is it entirely written in native code and consists of a single statically linked library, but its architecture also facilitates rapid integration of new features and logon tokens. Additionally, it offers customization options for its appearance and can be branded specifically for enterprise needs.
You can download the Aloaha Smart Login from: https://www.win-logon.com/aloaha_smart_login_home/