The openldap distribution includes a ldapdb auxprop plugin enabling SASL to fetch it's passwords from an LDAP directory. The plugin is licensed like openldap itself. There will be 2 new files in the files dir, ldapdb.c and README.ldapdb and a new ebuild based on cyrus-sasl-2.1.20-r1. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 49750 [details] new ebuild (should be -r2, at least)
Created attachment 49751 [details] README.ldap goes into ${FILESDIR}
Created attachment 49752 [details, diff] Makefile patch, goes into ${FILESDIR}
Created attachment 49753 [details] the plugin, goes into ${FILESDIR}
While I am the LDAP guy, I don't do SASL.
Sorry, I do not understand your comment. I doubt you compile Openldap without SASL and if so I'd be interested how do you provide the authentifications methods mandated by RFC 2829. I note that the sasldb plugin is only pulled in if ldap is in USE (same goes for saslauthd). Currently sasldb is the only way to provide shared secret MECHS for MTAs or cyrus if you have passwords in LDAP. IMO it's of great use WRT SSO and I haven't got the point yet why the fact that you don't need it should prevent others from using it. If I can do something in the LDAP/SASL area (e.g.getting 2.2 out the door) please contact me.
@comment#6, this bug assigned to Robin but he doesn't maintain cyrus-sasl, so he reassign back to net-mail.
As for getting OpenLDAP 2.2 out the door, I'm working on it, trust me (see 2.2.23 in CVS now, with a possible migration system).
There is a note in openldap CVS that ldapdb has been included upstream, will close this bug as soon as the plugin emerges in cyrus-sasl.
cyrus-sasl-2.1.21 is in CVS (will touch mirrors in a while). Please test and see if it fixes your problem. Cheers, Ferdy