Red Hat Bugzilla – Bug 245406
Last modified: 2007-11-30 17:12:08 EST
Description of problem:
I see in the spec file:
This seems to say that any App.conf files can be put in either dir
(/usr/lib/sasl2 or /etc/sasl2) or not?
but in my testing (specifically i'm using saslauthd with openldap) if my
slapd.conf is in /usr/lib/sasl2, then it is ignored. slapd/sasl tries to open
/etc/sasldb2 (the default i guess). When I move slapd.conf to /etc/sasl2, then
I get the correct call through to saslauthd.
This was on an install, not an upgrade, but I'm thinking this would break any
configured App.conf's that were in /usr/lib/sasl2/ on an upgrade.
Version-Release number of selected component (if applicable):
I don't know whether this happens or not on i386.
Steps to Reproduce:
1. configure an app for saslauthd (pwcheck_method: saslauthd) and put the
App.conf in /usr/lib/sasl2
2. authenticate... it won't work
3. put App.conf in /etc/sasl2
4. it works
failure to authenticate to configure check method.
authentice to configured check method
Ah, disregard, the path is supposed to be /usr/lib64/sasl2. that works fine.
sorry for the noise.