You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/16 10:37:39 UTC
[jira] [Resolved] (DIRSERVER-1701) ApacheDS doesn't return all the
attributes when invoking DirContext.getAttributes(Name, null)
[ https://issues.apache.org/jira/browse/DIRSERVER-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1701.
------------------------------------------
Resolution: Invalid
Assignee: (was: Alex Karasulu)
Pretty normal behavior : if neither '+' nor the expected operational attributes are provided in the request, only the user Attributes will be returned. This is plain compliant with the LDAP RFC.
> ApacheDS doesn't return all the attributes when invoking DirContext.getAttributes(Name, null)
> ----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1701
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1701
> Project: Directory ApacheDS
> Issue Type: Bug
> Environment: (javier@lenovo trunk)$ /opt/jdk1.6.0_25/bin/java -version
> java version "1.6.0_25"
> Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
> Java HotSpot(TM) Server VM (build 20.0-b11, mixed mode)
> (javier@lenovo trunk)$ cat /etc/issue
> Ubuntu 11.10 \n \l
> ApacheDS 2.0.0-M3
> Reporter: Javier Alcazar
>
> ApacheDS doesn't return all the attributes when invoking javax.naming.directory.DirContext.getAttributes(Name, null)
> Running some unit tests as described here: http://directory.apache.org/apacheds/1.5/42-using-apacheds-for-unit-tests.html
> Using a ldif file.
> When the following code is esecuted:
> ...
> env.put("java.naming.ldap.attributes.binary",
> ATTR_OBJECTSID +' '+ ATTR_OBJECTGUID+ ' '+"entryUUID");
> ctx = javax.naming.ldap.InitialLdapContext(env,null);
> .....
> attrIds = null;
> attrs = ctx.getAttributes(distinguishedName, attrIds);
> attrs doesn't contain ALL the attributes as specified by the JavaDoc
> attrIds - the identifiers of the attributes to retrieve. null indicates that all attributes should be retrieved;
> http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/DirContext.html#getAttributes(javax.naming.Name, java.lang.String[])
> Using the same code against other directory servers returns all the attributes.
> -----------
> Returned:
> dn: ou=3809,ou=system
> objectclass: organizationalUnit
> objectclass: top
> ou: 3809
> description: Description goes here
> l: testgroup@test.com
> postalcode: Group Name
> Expected:
> dn: ou=3809,ou=system
> objectclass: organizationalUnit
> objectclass: top
> ou: 3809
> description: Description goes here
> l: testgroup@test.com
> postalcode: Group Name
> createTimestamp: 20120316074659Z
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> entryCSN: 20120316074659.800000Z#000000#000#000000
> entryParentId: 1
> entryUUID:: ZjBkNDQ5NjUtMDMxMy00YWI2LTg5YzMtYzY0NDQ5N2YwOWVh
> -------
> Log:
> 6:49:38 [DEBUG] registries.DefaultSchemaObjectRegistry - Found ATTRIBUTE_TYPE ( 2.16.840.1.113730.3.1.34
> NAME 'ref'
> DESC namedref: subordinate referral URL
> EQUALITY caseExactMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
> USAGE distributedOperation
> )
> with oid: ref (DefaultSchemaObjectRegistry.java:181)
> 16:49:38 [DEBUG] handlers.SearchHandler - Sending ou=3809,ou=system (SearchHandler.java:401)
> 16:49:38 [DEBUG] filterchain.IoFilterEvent - Event MESSAGE_RECEIVED has been fired for session 3 (IoFilterEvent.java:118)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira