2026-11-10 · Beta
CodeB SmartLogin beta: one card for several accounts, Admin Console, temporary cards, full audit trail.
The beta of 10 November 2026, compared with the live version of August 2026. Download it as the
Tools edition or the
Systray (recent builds — tested, not yet code-signed).
Read the upgrade notes before rolling it out.
2026-11-10 · Beta · Cards
One card, several accounts — with an account picker at the logon screen.
A card linked to several Active Directory accounts now logs on to the account whose Windows
“Log On To” list names the PC, or to the only unrestricted account; otherwise the tap shows an
Account list with the default account preselected — pick it and press Enter. Linking a
card that is already on another account now warns, in the enrolment tools, the command-line tool and the
Admin Console. See one card, several accounts.
2026-11-10 · Beta · Administration
New CodeB Admin Console, temporary cards and logon-screen tools.
The CodeB Admin Console puts the cards linked in Active Directory,
the cards stored on the PC, the logon log and the tile logo in one window. Cards can get a
valid-from and valid-until date for visitors and contractors;
outside that window they are refused and the refusal is logged. Optionally the CodeB tile shows the computer
name and a System information link (IP, gateway,
DNS, MAC), with release/renew IP links — all off by default.
2026-11-10 · Beta · Audit & security
Audit trail in the Windows event log, and DPAPI-NG for stored credentials.
The log CodeB Credential Provider V2 now records 1100 logon/unlock, 1101 failed,
1102 temporary card refused and 1103 unknown card presented — never a PIN or
password, ready for event forwarding and SIEM (audit events).
Card token files are protected with Windows DPAPI-NG, so they open only on this PC, on the domain’s
computers and for the token’s user; the Web SSO password store is encrypted per user the same way
(how tokens are protected).
2026-11-10 · Beta · Web SSO, card removal, Bluetooth
Web SSO follows the user; lock and log-off on card removal work everywhere.
The Web SSO store follows the user to other PCs through the
shared data folder, and companies can add the optional
central Web SSO server to manage shared website logins per AD group.
Lock or log off on card removal now also works after a certificate-based (Kerberos) card logon; T2med can log
the user off about 3 seconds after the card is removed; and a short tap still logs on even when the card is
lifted before it was fully read. Bluetooth: several devices per user, Bluetooth Low Energy, and a new
“presence only” mode that needs no pairing.
2026-11-10 · Beta · Other improvements
NumLock, accented names, new command-line switches, a renamed tray.
- NumLock is switched on at the CodeB tile, for PINs on the number pad (can be switched off).
- User names and passwords with accents and special letters (for example “João”, “Ċarmela”) work with all token types.
- Command-line tool:
/updatecards sets a new password in all card tokens of a user; /validfrom, /validuntil, /logonto, /showlogonto (reference).
- The tray is now called CodeB SmartLogin, with Online Help, Online Meeting, About and a link to the CodeB Wallet; every menu item can be hidden by the administrator; sharp on high-DPI screens.
- Phone as logon card, and app links now point to the CodeB Wallet page.
2026-11-10 · Beta · Fixes
Fixes.
- Unlocking the PC with a card works, and tapping the card logs on without pressing Enter.
- The logon screen shows the card’s user, even when another user’s tile was selected.
- No logon/logoff loop after a reboot with automatic logon; automatic logon also works when the user has no tile yet.
- Removing one card no longer affects another card whose number starts the same way.
- After a wrong PIN the error appears at once (no 30-second wait) and the reader keeps working.
- Card readers that appear late (for example over Remote Desktop) are detected.
- Much faster logon screen when the domain controller cannot be reached — seconds instead of up to two minutes — for laptops on the road.
2026-11-10 · Beta · Upgrade notes
Before you upgrade.
- Install the new version, then restart the PC — Windows keeps the old logon component loaded until then.
- Update all PCs that share a data folder before enrolling new cards: older versions cannot read the protected card tokens. Alternatively set
HKLM\SOFTWARE\WOW6432Node\CodeB\Config\ProtectCardTokens = 0 until all PCs are updated.
- Users whose name or password contains accents or special letters must enrol their card or token once more.
- On some PCs the Systray must be started once with “Run as administrator” after the upgrade, so it can move to its new protected location under Program Files.
2026-10-07 · C122
Card revocation across computers, hardened.
A follow-up to the card- and token-sync release
(RemoteDataFolder).
A revoked card can no longer be brought back by dropping an old token file on the share — a newer
copy of a revoked token is accepted only from an administrator, a computer, or the user who deleted it.
NFCAdmin and the command-line admin tool now warn when a revocation or re-enrolment could not be written
to the share (typically because the administrator lacks rights on the file server). Offline laptops sign
in without waiting — an unreachable share is checked for at most about three seconds — and the
deleted record folders on the share are now created by the computers themselves, so no user
can own or tamper with them.
2026-10-07 · C120
Accented and national letters in card credentials.
User names and passwords that contain letters such as ç, ã, ä, ö, ß,
ċ, ġ, ħ or ż are now stored correctly on NFC card, USB-stick, Bluetooth
and TOTP tokens. Before, these letters were replaced by “?”, so affected users could not
sign in with a token. Typing the password at the logon screen, cards stored in Active Directory, and
Web SSO were never affected. If a card or token was enrolled with an older version, enrol it once
more after updating. See the
support FAQ.
2026-10-07 · C119
The sign-in screen shows the card owner.
Tap your card while a colleague’s tile is selected and the “signing in” screen now
shows your own name and picture rather than theirs — on the logon screen, when you already have a
tile of your own. The account opened is always the card’s. Unlocking a locked PC is unchanged.
2026-10-07 · C112–C118
Sync cards and tokens across computers, with roaming Web SSO.
Point every computer at one file share (RemoteDataFolder) and NFC cards, TOTP and
Bluetooth tokens, certificates and each user’s Web SSO logins stay in sync across the fleet:
central enrolment, authorization-checked fleet-wide revocation, owner-fenced Web SSO folders, and
sign-in that still works when the share is down. See
sharing cards and tokens across computers.
2026-10-07 · C108–C110
T2med card logon and log-off on card removal.
Assign one or more NFC cards to a T2med account in the CodeB Web SSO manager: T2med signs in while an
assigned card is on the reader, and — with one box ticked — logs the user out of T2med
about three seconds after the card is removed. See the
T2med case study.