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

Re: Can not add aliases with schema checking on (ITS#3017)

This is a multi-part message in MIME format.
--------------070102030307060300080409
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

The behavior has changed so ether it was a bug or it is now a bug.   

I've not seen any requirement in any RFC or other implementation for the 
naming attribute of an alias to exist in the alais object itself.  The 
effect is quite significant in that stops the use of aliases if schema 
checking is on.  As the use of aliases IS part of an RFC this makes the 
implementation non compliant. This indicates to me that it is a current bug.

I agree that the implentation of aliases is an issue that need carefull 
consideration.  Schema checking should treat aliases as a special case 
(they are a special type so this makes sence).

Tom

Pierangelo Masarati wrote:

>>Full_Name: Tom Hallam
>>Version: 2.1.25
>>OS: Solaris
>>URL: ftp://ftp.openldap.org/incoming/
>>Submission from: (NULL) (130.95.208.6)
>>
>>
>>If schema checking is on you can not add an alias as the server refuses
>>to add an object without a valid naming attribute.
>>
>>    naming attribute 'uid' is not present in entry
>>
>>If you try to add the attribute it refuses to add it as it is not valid
>>for the alias object class.
>>
>>    attribute 'uid' not allowed
>>
>>This behaviour seems to have changed from version 2.1.12
>>
>>Turning schema checking off fixes issue.
>>
>>Naming attributes should not be required for aliases when schema
>>checking is on.
>>    
>>
>
>This is not a bug in OpenLDAP's software;
>it might be considered a flaw in alias
>design.
>
>As a workaround, add
>
>objectClass: extensibleObject
>uid: <your entry's naming uid>
>
>to the entry.
>
>p.
>
>  
>

--------------070102030307060300080409
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
The behavior has changed so ether it was a bug or it is now a bug.    

I've not seen any requirement in any RFC or other implementation for the naming attribute of an alias to exist in the alais object itself.  The effect is quite significant in that stops the use of aliases if schema checking is on.  As the use of aliases IS part of an RFC this makes the implementation non compliant. This indicates to me that it is a current bug.

I agree that the implentation of aliases is an issue that need carefull consideration.  Schema checking should treat aliases as a special case (they are a special type so this makes sence). 

Tom

Pierangelo Masarati wrote:

Full_Name: Tom Hallam
Version: 2.1.25
OS: Solaris
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (130.95.208.6)


If schema checking is on you can not add an alias as the server refuses
to add an object without a valid naming attribute.

    naming attribute 'uid' is not present in entry

If you try to add the attribute it refuses to add it as it is not valid
for the alias object class.

    attribute 'uid' not allowed

This behaviour seems to have changed from version 2.1.12

Turning schema checking off fixes issue.

Naming attributes should not be required for aliases when schema
checking is on.
    


This is not a bug in OpenLDAP's software;
it might be considered a flaw in alias
design.

As a workaround, add

objectClass: extensibleObject
uid: <your entry's naming uid>

to the entry.

p.

  

--------------070102030307060300080409--