Loading...
Loading...
Generic LDAP users are no longer able to login after firmware downgrade.
Firmware version 1.30.10.50 introduces a change in how the Generic LDAP BIND account password is stored: Before 1.30.10.50: The BIND password is stored in the database as plaintext . Starting in 1.30.10.50: The BIND password is stored only in encrypted form, and the plaintext field is purged . When the system is downgraded: The firmware reverts to using the old plaintext field. However, the plaintext value no longer exists because it was purged during the 1.30.10.50 update. The encrypted password remains, but older firmware versions cannot read or use it. As a result, LDAP authentication fails after downgrading.
To restore LDAP functionality, use one of the following options: Option 1: Upgrade back to firmware 1.30.10.50. Reinstalling firmware 1.30.10.50 (or newer) allows the system to use the already‑stored encrypted BIND password. LDAP authentication resumes working without additional configuration. Option 2: Reenter the LDAP BIND account password Older firmware relies on the plaintext password field, so the user must repopulate it. Note: Updating the BIND password to the same value does not trigger the attribute-change notification required to rewrite the plaintext field. Therefore, this must be done in two steps : Change the BIND account password to any temporary value. This forces a database update Change the password again back to the correct value. This populates the plaintext field, enabling LDAP authentication to work.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.