directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quanah Gibson-Mount (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-513) Do delete before add when modifying attribute values
Date Fri, 21 Aug 2009 16:18:14 GMT


Quanah Gibson-Mount commented on DIRSTUDIO-513:


I think the problem is more that some people choose to hide their schema from being read out
of the subschema entry, which is a perfectly valid thing to do.  So any well written LDAP
client needs to be able to work with the fact that the schema may or may not be browsable.
 There is even some security suite out there that "warns" people that exposing the subschema
entry is a security risk.  Not that I agree with it. ;)

> Do delete before add when modifying attribute values
> ----------------------------------------------------
>                 Key: DIRSTUDIO-513
>                 URL:
>             Project: Directory Studio
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Martin Alderson
>            Priority: Minor
> When connecting to Novell eDirectory and modifying the schema an "Attribute Or Value
Exists" error occurs.  This is due to the modification performing an add before the delete
and eDirectory (wrongly) complains that the same OID has been used more than once before realising
that the old value should be deleted.  Note that this is a problem with eDirectory but it
would be useful if Studio asked for the delete to be performed before the add when modifying
an attribute value which eDirectory is OK with.
> An example of the LDIF in the modifications logs view for an operation that fails is:
> dn: cn=schema
> changetype: modify
> add: objectClasses
> objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' [ value...]
> -
> delete: objectClasses
> objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' [...old value...]
> -
> It also seems that modifying the schema on ApacheDS has the same issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message