Skip to main content

SecureAuth Connector release notes

This page documents changes in each SecureAuth Connector release. Upgrading from version 2.1.4 to 2.2.1 delivers approximately 4x throughput and 4x faster response times, with zero-error reliability maintained throughout.

See SecureAuth Connector installation and SecureAuth Connector update.SecureAuth Connector installation

Version 2.2.1

  • Bug fix: Resolved an issue where configuration properties could be saved with incorrect data types, preventing potential configuration errors.

Version 2.2.0

Caching

The installer now includes a cache configuration step. During installation or upgrade, you can select a caching mode for the Connector service:

  • No Caching. The Connector retrieves user data directly from the data store on every authentication request.

  • In Memory. The Connector stores user data in memory for 30 minutes, resetting the timeout each time the same user authenticates. The Connector only queries the data store for save operations like lock, unlock, or property updates. This is the default.

  • Redis. Same behavior as In Memory, but stores the cache in a Redis instance. You provide a connection string during installation, and the installer validates the connection.

Caching reduces the number of queries to Active Directory and other data stores during authentication, which helps with performance under high authentication loads.

Messaging and reliability

  • Asynchronous message processing: internal message handling no longer blocks while waiting for responses, freeing the Connector to process other requests during wait times.

  • Upgraded RabbitMQ client for improved connection stability and message delivery reliability.

  • Pod queue reply messaging for more robust communication between the Connector and the SecureAuth cloud platform.

Installation

  • Modernized installer upgraded to WiX 6 for a more reliable and streamlined installation experience.

Version 2.1.6

  • Added lock and protect section validations to ensure that locked and protected configuration sections are properly enforced, preventing unauthorized modifications.

Version 2.1.5

  • Multi-threaded request processing: the Connector now handles multiple authentication requests simultaneously, making full use of available server resources.

In this section: