Thanks to all for your help.
I finally downloaded the correct patch, and applied it to sasl.
Everything is working like a charm - 8 cyrus servers running on 1 machine, all
using the -C config option with 8 different config files, all configs pointing
to a different basedn in the ldap tree. It d
From: "John C. Amodeo" <[EMAIL PROTECTED]>
> One other question to add to my previous e-mail. Are you supposed to use
the "Cyrus LDAP
> auth patch" or the "Cyrus SASL 1.5.24 LDAP auth and mysql patch"?
>
Use the LDAP + MySQL patch.
> If you have to use the "Cyrus SASL 1.5.24 LDAP auth and mysql
Sorry,
One other question to add to my previous e-mail. Are you supposed to use the "Cyrus
LDAP
auth patch" or the "Cyrus SASL 1.5.24 LDAP auth and mysql patch"?
If you have to use the "Cyrus SASL 1.5.24 LDAP auth and mysql patch" do you have a
modified version minus the mysql stuff, or is it
On Thu, 12 Apr 2001, John C. Amodeo wrote:
> A quick question...
>
> We downloaded the patches form Openldap.org, but looking at the source, there are no
> provisions to pass ldap_server or ldap_basedn. Am I missing something here? The
> code in the pwcheck_ldap.c suggests that you need to hard
A quick question...
We downloaded the patches form Openldap.org, but looking at the source, there are no
provisions to pass ldap_server or ldap_basedn. Am I missing something here? The
code in the pwcheck_ldap.c suggests that you need to hard-code the ldap information
in, then compile.
We are
> But with Cyrus, I need to somehow pass information up the stack pertaining
> to the IP address the request came from. In turn, with a pam_ldap module
> that is IP-address aware, I can switch directory trees based on IP-address
> and I think my problem will be solved.
>
> In other words, say I
