[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: errant SASL/GSSAPI setup?

To: Quanah Gibson-Mount <quanah@stanford.edu>
Subject: Re: errant SASL/GSSAPI setup?
From: "Allan E. Johannesen" <aej@WPI.EDU>
Date: Wed, 30 Aug 2006 12:57:35 -0400
Cc: openldap-software@OpenLDAP.org, "Allan E. Johannesen" <aej@WPI.EDU>
In-reply-to: <4701598B1BFFD28772B3EB82@SW-90-717-287-3.stanford.edu>
References: <17653.40565.650621.785696@CCC1.WPI.EDU> <052DD991EEBBEE947896C36E@SW-90-717-287-3.stanford.edu> <17653.48794.770031.999647@CCC1.WPI.EDU> <E940E156DA412F0443F630FF@SW-90-717-287-3.stanford.edu> <4701598B1BFFD28772B3EB82@SW-90-717-287-3.stanford.edu>

>>>>> "quanah" == Quanah Gibson-Mount <quanah@stanford.edu> writes:

quanah> --On Wednesday, August 30, 2006 9:47 AM -0700 Quanah Gibson-Mount
quanah> <quanah@stanford.edu> wrote:

>> 
>> 
>> --On Wednesday, August 30, 2006 12:36 PM -0400 "Allan E. Johannesen"
>> <aej@WPI.EDU> wrote:
>> 
>> 
>> 
>>> Thanks for looking into the problem.

quanah> BTW, your syncrepl definition is missing the saslmech.

Yes, I should put that in there.  I just trimmed the "simple" stuff
(dn/password) out and put in "sasl".  I should have specified the mechanism.

Nothing else could work in my instance, anyway.

Follow-Ups:
- Re: errant SASL/GSSAPI setup?
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

References:
- errant SASL/GSSAPI setup?
  - From: "Allan E. Johannesen" <aej@WPI.EDU>
- Re: errant SASL/GSSAPI setup?
  - From: Quanah Gibson-Mount <quanah@stanford.edu>
- Re: errant SASL/GSSAPI setup?
  - From: "Allan E. Johannesen" <aej@WPI.EDU>
- Re: errant SASL/GSSAPI setup?
  - From: Quanah Gibson-Mount <quanah@stanford.edu>
- Re: errant SASL/GSSAPI setup?
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

Prev by Date: Re: errant SASL/GSSAPI setup?
Next by Date: Re: errant SASL/GSSAPI setup?
Index(es):
- Chronological
- Thread