Thanks for the response. It's an issue because there are certain accounts we want to
auth directly with ldap since using sasl is much slower. However, with our current setup
they are all going through sasl first.
Is ldap unable to assign a priority to a password entry?
----- Original Message -----
From: "Clément Oudot" <clement.oudot(a)worteks.com>
To: "Jeremy Diaz" <jeremy.diaz(a)rexconsulting.net>
Cc: "openldap-technical" <openldap-technical(a)openldap.org>
Sent: Tuesday, November 26, 2019 9:20:25 AM
Subject: Re: Is there a way to set a preference on entries with multiple userPassword
Le 2019-11-20 21:40, Jeremy Diaz a écrit :
Currently I have ldap entries with 2 userPassword attributes. One is a
regular SHA password which the other one delegates to sasl. However
results in all entries binding through sasl rather than locally. I
some entries to default to sasl and other entries to default to SHA
still failover to the other password entry. Is this possible through
I have done some tests. I confirm that you can have 2 userPassword
values, one SASL and the other regular. When you BIND with a password,
it seems all values are tested, and if one match, then the BIND is
successful. I don't see how you can select an order in the passwords.
But why is it a problem? With this setup, you can use SASL or regular
password for an entry, and the failback will work.
This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the
following link to report this email as spam: