directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Closed: (DIRSERVER-704) Values in operational attributes creatorsName and modifiersName contain OID instead of attribute name
Date Wed, 16 Aug 2006 17:12:17 GMT
     [ ]

Alex Karasulu closed DIRSERVER-704.

    Fix Version/s: 1.1.0
       Resolution: Fixed

Committed for 1.0 on this revision:

Committed for 1.1 on this revision:

Now there is a new configuration option to turn on and off the denormalization of the creatorsName
and the modifiersName.  Note that by default this denormalization is turned off to save on
processing.  To turn it on set the following property in the startup configurtion bean of
the server.xml file:

    <property name="denormalizeOpAttrsEnabled"><value>false</value></property>

> Values in operational attributes creatorsName and modifiersName contain OID instead of
attribute name
> -----------------------------------------------------------------------------------------------------
>                 Key: DIRSERVER-704
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC4
>         Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
>            Reporter: Stefan Zoerner
>         Assigned To: Alex Karasulu
>            Priority: Minor
>             Fix For: 1.1.0, 1.0-RC4
> If I create an entry and perform a modification on it, the values of the operational
attributes creatorsName and modifiersName contain OIDs instead of attribute names:
> $ ldapsearch -D "uid=admin,ou=system" -w ****** -b "cn=Kate Bush,dc=example,dc=com" -s
base "(objectClass=*)" "*" "+"
> version: 1
> dn: cn=Kate Bush,dc=example,dc=com
> createTimestamp: 20060810092457Z
> modifiersName: 0.9.2342.19200300.100.1.1=admin,
> modifyTimestamp: 20060810093218Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Kate Bush
> I am not sure, whether this is a defect. But it looks strange to me, I have never seen
an LDAP server which does it that way, and the behavior in Apache Directory Server was also
different in earlier versions (i.e. creatorsName: uid=admin,ou=system).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message