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.2 (released June 22nd 2020)
- 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)
- 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.
- 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
- 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
- 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
- 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
- Possibility of configuring a blacklist that excludes certain domains from registration
- 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
- The setup requires the Token Engine version 1.1 or higher.
- Secure Logon now uses .NET Framework 4.6
- 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.
- Bug in setup fixed (links with same ID)
- The setup contains additional parameters to control the reboot
- The setups contain only the Secure Logon 2.0 components and no Token Engine anymore.