Update Your System With LogonBox SSPR 2.3.18

Windows two-factor authentication

Introduction

LogonBox is pleased to announce the immediate availability of LogonBox SSPR 2.3.18.
This release includes secure Node improvements and support for following AD referrals for child domains.

Secure Node improvements

A memory leak in Secure Node, caused by not successfully closing down all opened connections, has been fixed. Secure Node now correctly closes all connections once they are no longer required.

The Secure Node client installer executable now performs an uninstall of the previous version before upgrading, which provides a better upgrade experience.

AD referrals

If you turn on the option for Follow Referrals in Configure User Database->Advanced, LogonBox will now follow any referrals that AD references.
This setting allows you to synchronize users from any child domains.

NOTE: You must connect to a global catalog server for this to work, and you must define the global catalog port 3269 in the hostname field (i.e. adserverhost:3269)

Upgrade Instructions

You can directly upgrade from the web UI or the operating system.

To upgrade from the web UI, log on with your admin account, navigate to Server Status from the main dashboard and click Update. You may also be prompted automatically on login if you have Updates, Features & Licensing->Update Prompt turned on.

To upgrade from the operating system:

On Windows – download the new installer, run the installer, and follow the prompts.

On a LogonBox VM – from a shell, type in:

apt update
apt upgrade

If you are still running a version before 2.3, you will need to perform some extra steps from the OS, as detailed here:

https://docs.logonbox.com/app/manpage/en/article/6172513

Our support team will upgrade Cloud customers over the coming week.

Changes

Here is a summary of the changes in this release.

Features

  • AD syncs now follow referrals if you add the global catalog port to the hostname (i.e. adhostname:3269)
  • Secure Node clients upgrade more cleanly

Bugs

  • Fixed a memory leak with Secure Node connections