You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2006/08/10 11:41:15 UTC
[jira] Created: (DIRSERVER-704) Values in operational attributes
creatorsName and modifiersName contain OID instead of attribute name
Values in operational attributes creatorsName and modifiersName contain OID instead of attribute name
-----------------------------------------------------------------------------------------------------
Key: DIRSERVER-704
URL: http://issues.apache.org/jira/browse/DIRSERVER-704
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
Priority: Minor
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,2.5.4.11=system
modifyTimestamp: 20060810093218Z
creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DIRSERVER-704) Values in operational attributes
creatorsName and modifiersName contain OID instead of attribute name
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-704?page=comments#action_12428386 ]
Alex Karasulu commented on DIRSERVER-704:
-----------------------------------------
We can make a filtering enumeration do the conversion on the way out the door. We can make this a configurable parameter so it can be turned on and off.
> Values in operational attributes creatorsName and modifiersName contain OID instead of attribute name
> -----------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-704
> URL: http://issues.apache.org/jira/browse/DIRSERVER-704
> 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
> Priority: Minor
>
> 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,2.5.4.11=system
> modifyTimestamp: 20060810093218Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DIRSERVER-704) Values in operational attributes
creatorsName and modifiersName contain OID instead of attribute name
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-704?page=comments#action_12427591 ]
Alex Karasulu commented on DIRSERVER-704:
-----------------------------------------
This makes certain operations much faster even though it does look odd. We recently started using this when we normalized to use OIDs.
I guess we should discuss whether or not this should be kept this way. It is very odd.
> Values in operational attributes creatorsName and modifiersName contain OID instead of attribute name
> -----------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-704
> URL: http://issues.apache.org/jira/browse/DIRSERVER-704
> 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
> Priority: Minor
>
> 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,2.5.4.11=system
> modifyTimestamp: 20060810093218Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DIRSERVER-704) Values in operational attributes
creatorsName and modifiersName contain OID instead of attribute name
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-704?page=all ]
Alex Karasulu closed DIRSERVER-704.
-----------------------------------
Fix Version/s: 1.1.0
1.0-RC4
Resolution: Fixed
Committed for 1.0 on this revision:
http://svn.apache.org/viewvc?view=rev&revision=431946
Committed for 1.1 on this revision:
http://svn.apache.org/viewvc?view=rev&revision=431951
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: http://issues.apache.org/jira/browse/DIRSERVER-704
> 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,2.5.4.11=system
> modifyTimestamp: 20060810093218Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DIRSERVER-704) Values in operational attributes
creatorsName and modifiersName contain OID instead of attribute name
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-704?page=all ]
Alex Karasulu reassigned DIRSERVER-704:
---------------------------------------
Assignee: Alex Karasulu
> Values in operational attributes creatorsName and modifiersName contain OID instead of attribute name
> -----------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-704
> URL: http://issues.apache.org/jira/browse/DIRSERVER-704
> 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
>
> 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,2.5.4.11=system
> modifyTimestamp: 20060810093218Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DIRSERVER-704) Values in operational attributes
creatorsName and modifiersName contain OID instead of attribute name
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-704?page=comments#action_12428382 ]
Emmanuel Lecharny commented on DIRSERVER-704:
---------------------------------------------
This is because internally, we don't use any other form than the OID form. We may need to add a layer to transform this OID to use the first alias, or may be we can use the upName if it is stored.
> Values in operational attributes creatorsName and modifiersName contain OID instead of attribute name
> -----------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-704
> URL: http://issues.apache.org/jira/browse/DIRSERVER-704
> 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
> Priority: Minor
>
> 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,2.5.4.11=system
> modifyTimestamp: 20060810093218Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira