Ascender Pro v1.1.2 Release Notes

Released: September 29, 2026

Features

Added a Bind Account and Bind Password to the LDAP settings, replacing the former Test Bind fields. When a Bind Account is configured it is used to confirm that the user exists and to evaluate required group membership, and the user's own credential is used only to verify the login. This is required when the directory issues one-time or multi-factor passwords. Leaving both fields empty keeps the previous behavior, and the Test button then connects with an anonymous bind.
The Require Group field now accepts the name of the group rather than its full Distinguished Name. A warning is shown if a Distinguished Name is entered, and the value is still saved.

Fixed LDAP login for directories that issue one-time or multi-factor passwords. A first-time login performed two separate binds as the user, one to verify the credential and a second to create the local account. Where the password included a one-time code the second bind always failed, because the code had already been consumed, leaving the session without a matching account. Directory lookups now run under the Bind Account, so the user's credential is used exactly once.
Fixed SAML group attributes being overwritten when an Identity Provider sent more than one group attribute. Each attribute replaced the values before it, so only the last was applied. The values are now combined.
Fixed a fatal error that occurred on every page when a session was left without a matching local account, which made the interface unusable until browser cookies were cleared.