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

Re: (ITS#3472) return code should be 32 when no access to object

To: Pierangelo Masarati <ando@sys-net.it>
Subject: Re: (ITS#3472) return code should be 32 when no access to object
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Sun, 09 Jan 2005 21:09:51 -0800
Cc: quanah@stanford.edu, openldap-devel@OpenLDAP.org
In-reply-to: <41E146F2.8060607@sys-net.it>
References: <200501080059.j080xbi0027275@boole.openldap.org> <6.2.0.14.0.20050107202757.02a4d308@mail.openldap.org> <41E146F2.8060607@sys-net.it>

At 07:00 AM 1/9/2005, Pierangelo Masarati wrote:
>Kurt D. Zeilenga wrote:
>
>>I've added the basic parse code for "disclose" and "+d", appreciate
>>help in implementing this.
>> 
>I'll do some work on this; candidate for development will be ITS#3432 item 7 (back-sql structuralObjectClass modification), of course trying to make things as general as possible, and moving to frontend all code tht may be of common use for other backends.

Yes, I'll need to some frontend work before "manage" can be
realized.  However, "disclose on error" (disclose) and
"don't disclose on error" (none) can be implemented now in
backends.

>p.
>
>
>
>
>   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497

Follow-Ups:
- Re: (ITS#3472) return code should be 32 when no access to object
  - From: Pierangelo Masarati <ando@sys-net.it>

References:
- Re: (ITS#3472) return code should be 32 when no access to object
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: (ITS#3472) return code should be 32 when no access to object
  - From: Pierangelo Masarati <ando@sys-net.it>

Prev by Date: Re: (ITS#3472) return code should be 32 when no access to object
Next by Date: Re: redesigning the client API
Index(es):
- Chronological
- Thread