Re: RE : (ITS#3450) Modify RDN returns Naming Violation.

[ando@sys-net.it]

I ran the operation you're reporting a failure for on REL_ENG_2_2 (which,
I admit, may differ from 2.2.19, but I think the differences should not
affect this problem) either with and without write permission, and I
always see the appropriate behavior.  At this point, you should really
send your ACLs, to determine what missing write permission is triggering
the erroneous error reporting.  I?ve been trying with

access to *
    by users read

and

access to *
    by users write

The latter lets the operation succeed, while the former makes it fail
quite early, when accessing the old entry's "entry" pseudo-attribute.

p.

> I still have the problem with 2.2.19 (error is naming violation instead of
> insufficient acces rights).


-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it


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