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 2007/05/10 13:18:15 UTC

[jira] Created: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

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


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.


[jira] Closed: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Zoerner closed DIRSTUDIO-97.
-----------------------------------


Confirmed. It is now possible to view the attributes of a CN=SCHEMA of a TivoliDS 6 entry within Directory Studio (I have tested this with 1.1.0.v20080303).

> 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 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
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.1.0
>
>         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.


[jira] Commented: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577502#action_12577502 ] 

Pierre-Arnaud Marcelot commented on DIRSTUDIO-97:
-------------------------------------------------

Stefan, is this issue still present in the latest 1.1.0 RC2 version of Studio ?
Thanks.

> 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 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
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.1.0
>
>         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.


[jira] Updated: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seelmann updated DIRSTUDIO-97:
-------------------------------------

    Fix Version/s: 1.1.0
         Assignee: Stefan Seelmann

Stefan, could you please check if this issue is fixed in the current trunk version?

> 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 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
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.1.0
>
>         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.


[jira] Updated: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Attachment: DIRSTUDIO-97.ldif

Search result of query against TivoliDS 6.0, command line
$ ldapsearch -h degas -p 389 -b cn=schema -s base "(objectClass=*)" * objectClass > DIRSTUDIO-97.ldif
 

> 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
>
>
> 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.


[jira] Resolved: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seelmann resolved DIRSTUDIO-97.
--------------------------------------

    Resolution: Fixed

This should be fixed, there was a pb with case sensitiveness (cn=schema vs. CN=SCHEMA) when comparing DN's. Now we use the LdapDN class from shared-ldap and compare normalized DNs.


> 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 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
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.1.0
>
>         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.


[jira] Commented: (DIRSTUDIO-97) Unable to display attributes of subschemasubentry cn=schema of TivoliDS 6.0 in Entry Editor

Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSTUDIO-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582440#action_12582440 ] 

Stefan Zoerner commented on DIRSTUDIO-97:
-----------------------------------------

I'll retest this one the next days -- I'll need access to a TivoliDS 6.0 for that -- Sorry for the delay.

> 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 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
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.1.0
>
>         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.