[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Zoerner updated DIRSTUDIO-97:
------------------------------------

    Attachment: screenshot-1.jpg

No Attribute values displayed in Entry Editor for CN=SCHEMA

> Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 
> in Entry Editor
> -------------------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-97
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-97
>             Project: Directory LDAP Studio
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>         Environment: LDAP Studio 0.8.0 on Windows XP Professional SP 2
> IBM Tivoli Directory Server 6.0 on Sun Solaris 9 (SPARC)
>            Reporter: Stefan Zoerner
>            Priority: Minor
>         Attachments: DIRSTUDIO-97.ldif, screenshot-1.jpg
>
>
> For some reason, LS is unable to display the attributes of the 
> subschemasubentry (cn=schema), if conntected to a TivoliDS 6.0.
> I have analyzed the situation with Wireshark and found out, that the 
> following request is performed by LS:
> protocolOp: searchRequest (3)
> searchRequest
> baseObject: CN=SCHEMA
> scope: baseObject (0)
> derefAliases: neverDerefAliases (0)
> sizeLimit: 0
> timeLimit: 0
> typesOnly: False
> Filter: (objectClass=*)
> attributes: 2 items
>     Item: *
>     Item: objectClass
> If performed against TivoliDS, according to Wireshark the schema elements are 
> returned to LS (an entry of size >500k), but no attribute is displayed at all 
> (even cn is missing). It makes no difference, whether the option "Show 
> Operational Attributes" is enabled or not. No attribute values are displayed 
> in the Entry Editor. I have included an LDIF with the search result and a 
> Screen Shot of LS. 
> Please note that the Schema Browser of LS perfectly shows all Schema elements 
> on the same connection. 

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

Reply via email to