Release Notes

The release notes provide information about the changes made to Secure Logon™ 2.0 in the respective version. Sorted by version number, the changes are categorized by topic. In addition to new functions and fixed errors, changes to functions that affect the use of the software are also described.

Version 2.5.9 (released April 16th 2024)

Fixed an issue logging the token serial number.
A problem in the DESFire module that occurred in connection with different application IDs has been fixed.
Fixed an issue in the DESFire module that could occur in conjunction with Cherry card readers.

Version 2.5.8 (released July 6th 2023)

Secure Logon 2.0 Manager now asks for confirmation before formatting a token.
The “Current password” menu item in the notification area of the taskbar can now be hidden administratively.
A problem with determining the currently installed setup version has been fixed.
Fixed an issue in password change scenarios when the password on the token is wrong and UseOldPasswordFromToken is active.
When correcting an incorrect password on the token, the provider no longer requires confirmation of the password.
An issue with offline login with domain accounts has been fixed.
Token Engine Manager now asks for confirmation before formatting a token.
The YubiKey module now uses its own registry branch for settings and policy. Previously settings of the I2C module were applied.
Fixed a problem that prevented a SetPIN right after initialization
YubiKey: Increased stability
DESFire: Increased stability (especially for EV2 and EV3)

Version 2.5.7 (released January 17th 2023)

.NET Framework 4.7.2 is now required for using Smart Logon.
The digitronic Relay Service version 1.2.0 or higher is required for the use of SmartToken.
SmartToken can now also be used on terminal servers. The behavior of the token has been adapted to the use of hardware tokens (a SmartToken can only ever be connected in one user session).
RemoteConnectivityAssistant is now installed with SmartToken. This application starts automatically and enables a connection to be established between the SmartToken and the PC for other applications (e.g. HiCrypt).
When using DESFire tokens, a read-only mode can now be used (by using the token serial number) if write access to the token is not possible.
When accessing an LDAP server (in token-read-only mode), authentication can take place in the current user context (negotiation).
Fixed a bug that did not correctly determine the segmentation status of Legic tokens.
Fixed a bug where different error states were acknowledged with the same error message.

Version 2.5.6 (released July 4th 2022)

YubiKey can now also be connected via NFC.

Version 2.5.6 (released March 25th 2022)

Fixed a bug that could occur under certain conditions when unloading the credential provider.
Fixed a bug that happened during initialization of DESFire token.
Added auto-logon functionality after token presentation (requires additional software).
New: YubiKey (CCID) can be used as a token.

Version 2.5.5 (released August 30th 2021)

Requires Token Engine v.1.1.9 or newer
Supports Fast Object Extraction for better performance
Support of remote token modules (QR code support)
Fixed a bug that could lead to a deadlock during login (token removed during login)
Fixed a bug that prevented session monitoring when using a Microsoft account

Version 2.5.4 (released April 1st 2021)

Support for domains that are in a position of trust with others
Logon via SmartLogon™ possible across various locations even in highly complex IT infrastructures

Version 2.5.3 (released January 11th 2021)

Bugfixes:

Problem solved with passwords containing special characters
Problem solved with licenses which became invalid because of wrongly reported hardware changes

DESFire and I²C Token:

New PIN is valid as soon as 1 character has been changed

Version 2.5.2 (released June 22nd 2020)

General adjustments:

Logging of login attempts in Windows EventLog
Blacklist and Whitelist configuration provides blocking of token using their serial number (only configurable via Group Policy Templates)

Version 2.4.1 (released December 5th 2019)

General adjustments:

Token operations in the manager can be deactivated specifically
Configuration via group policies is fully supported
ADMX Group Policy Templates available (can be obtained on request from digitronic)

The following features can be enabled via Group Policy:

Countdown timer now offers the possibility to let the user choose the type of reaction (blocking / logoff)
The password of the current user logged on with a token can be displayed/copied.
Locked sessions can be automatically logged out after a certain period of time.

Version 2.3.0

Bug fixed that could cause token monitoring to be inactive on slow systems
Fixed a bug that caused the manager to crash when adding credentials
New license variant added: Floating License

Version 2.2.5

Adapted to the concept of PIN complexity
Fixed a bug that could cause the Secure Logon 2.0 Manager to crash when adding credentials
Fixed a bug that could cause the Check PIN dialog not to close when removing the token

Version 2.2.3 + 2.2.4

Features:

Settings can now be defined user-specifically
Settings dialog has been extended by most used options
Added a user settings dialog that allows a user without administrative rights to make settings.
Automatic check for a newer available version included (can be disabled)
You can now prevent a null PIN token from being used for logon.
Secure Logon 2.0 Installer supports silent installation
Secure Logon 2.0 Installer supports the provision of a product key

Bugfixes:

Secure Logon 2.0 Installer now correctly displays the texts in English language
Fixed a bug that could cause that no account could be linked to the token during the login process
Fixed a bug that could cause token monitoring not to become active despite a token login
Fixed a bug that could lead to incorrect focus setting in some dialogs

Version 2.2.1 + 2.2.2

Features:

Possibility of configuring a blacklist that excludes certain domains from registration

Bugfixes:

Use of user names and passwords with special characters are now possible
prevents the lock action from being bypassed when the port process is terminated.
Ability to use systems with a computer name that contains umlauts

Sonstiges:

The setup requires the Token Engine version 1.1 or higher.
Secure Logon now uses .NET Framework 4.6

Version 2.1.0

License dialogs in the manager can now be confirmed with Enter
The start of the manager as a non-administrative user can now be prevented
When a password is changed, the old password can be used by the token.
If several users exist on the token, the first user valid for the system is selected (logon).
Authentication at network drives possible
Tokens can be initialized during logon (if supported by the token).
Empty tokens can be linked to an account during login (application of credentials)
Configuration possible to log in with token + password and not with token + PIN
The reaction when removing the token can be delayed and visualized by a notifier with countdown.
The product key can be added to the setup during the rollout, which then leads to automated licensing and activation.
Proxy settings can now be entered in the Settings dialog
Service starts faster
Deactivation Key is also stored in the event log when uninstalling (if deactivation is not successful)
Display of setup version in About dialog
LDAP connection for tokens with UID (Mifare Classic) or Cardid (Legic) in combination with token + password added.

Version 2.0.18

Bug in setup fixed (links with same ID)

Version 2.0.17

The setup contains additional parameters to control the reboot

Version 2.0.16

The setups contain only the Secure Logon 2.0 components and no Token Engine anymore.