To authenticate to the LDAP server is the unique username and
corresponding password sufficient?  Or do we also need the context?

If we need the context, do we obtain it by querying the root DSE?

Does anonymous binding need to be allowed to get the root DSE?  And if
so, doesn't that defeat the purpose of having authentication?

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rich
Megginson
Sent: Thursday, March 09, 2006 5:32 PM
To: [email protected]
Subject: Re: Handling Failover

Standard8 wrote:
> Rich Megginson wrote:
> 
>> Standard8 wrote:
>>
>>> Rich Megginson wrote:
>>>
>>>> Michael Pratt wrote:
>>>>
>>>>> Thanks for the update Anton.  Do you know when a possible patch 
>>>>> would be ready?  We're trying to migrate to SSL as soon as we can,

>>>>> and due to the processes in place, I have to account for about a 
>>>>> week extra to bring in external source code and compile (unless
the 
>>>>> binaries are being distributed, but I didn't see any recent ones
on 
>>>>> the Mozilla FTP site).
>>>>
>>>>
>>>>
>>>> I'm going to put binaries for v5.17 as soon as I get ftp access, 
>>>> which should be any day now.
>>>
>>>
>>>
>>> Does that mean we've tagged the tree for v5.17 already?
>>
>>
>> I've made a preliminary tag for v5.17, which could become the
official 
>> tag if there's nothing else to do.  Did you have anything else in
mind 
>> for the short term?
> 
> 
> My only concern at the moment is that when SeaMonkey or Thunderbird 
> switch to xulrunner, the configure script will need to be changed (or 
> parameters posted to it (building with xulrunner means the nspr stuff
is 
> under objdir/xulrunner/.... But we could pick that up when its really 
> needed - its probably not urgent for another couple of months.

The new configure script is quite flexible in how it handles locations 
for nspr and nss.  In addition to the switches below, if DIST is set 
appropriately (e.g. $(DIST)/include/nspr and $(DIST)/lib) at make time, 
no changes should be required.

   --with-system-nss   Use system installed NSS
   --with-nss[=PATH]              Build libssldap, using NSS for crypto 
- optional PATH is path to NSS package
   --with-nss-inc=PATH        Netscape Portable Runtime (NSS) include 
file directory
   --with-nss-lib=PATH        Netscape Portable Runtime (NSS) library 
directory
   --with-nss-prefix=PFX  Prefix where NSS is installed
   --with-nss-exec-prefix=PFX
                           Exec prefix where NSS is installed
   --with-system-nspr   Use system installed NSPR
   --with-nspr=PATH        Netscape Portable Runtime (NSPR) directory
   --with-nspr-inc=PATH        Netscape Portable Runtime (NSPR) include 
file directory
   --with-nspr-lib=PATH        Netscape Portable Runtime (NSPR) library 
directory  --with-nspr-prefix=PFX  Prefix where NSPR is installed
   --with-nspr-exec-prefix=PFX
                           Exec prefix where NSPR is installed
_______________________________________________
dev-tech-ldap mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-ldap
_______________________________________________
dev-tech-ldap mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-ldap

Reply via email to