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

Re: gssapi service principal

To: Quanah Gibson-Mount <quanah@stanford.edu>
Subject: Re: gssapi service principal
From: Alex Moore <asmoore@edge.net>
Date: Fri, 2 Dec 2005 16:44:42 -0600
Cc: openldap-software mailing list <openldap-software@OpenLDAP.org>
In-reply-to: <F5C06667B24CC69D74705A20@cadabra-dsl.stanford.edu>
References: <20051130062541.00006a8c@sws602.mcsun.local> <EE560110E55FB33C0A2F4E50@cadabra-dsl.stanford.edu> <20051130141250.00000cd7@sws602> <F5C06667B24CC69D74705A20@cadabra-dsl.stanford.edu>

On Fri, 02 Dec 2005 10:26:27 -0800
Quanah Gibson-Mount <quanah@stanford.edu> wrote:

> 
> You really need to get the SASL server/client working *first*.  It is
> the SASL code that determines what OpenLDAP looks for, not the other
> way around.

Agreed. And Kurt has said this many times before as well.  So that is my
next step.


Thanks for the replies, Alex

References:
- Re: gssapi service principal
  - From: Alex Moore <asmoore@edge.net>
- Re: gssapi service principal
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

Prev by Date: RE: Linking against a specific Berkeley DB install
Next by Date: Re: Search on 'member' attribute in dynamic group
Index(es):
- Chronological
- Thread