Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-269

Attributes not displayed when browsing BEA Weblogic embedded LDAP

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0.1
    • Fix Version/s: 1.1.0
    • Component/s: studio-ldapbrowser
    • Labels:
      None
    • Environment:
      BEA Weblogic 8.1 embedded LDAP

      Description

      The LDAP browser will not display attributes for anything but the root DSE. Searches can still be made using known attributes. If new attributes are added to an entry they are viable until entry is refreshed. Other applications do not show similar difficulty in browsing ldap. Occurs on multiple platforms (Unix/Linux/Windows) with LDAP at various stages of maturity.

        Issue Links

          Activity

          Hide
          Pierre-Arnaud Marcelot added a comment -

          Version 1.1.0 has been released.
          Closing this issue.

          Show
          Pierre-Arnaud Marcelot added a comment - Version 1.1.0 has been released. Closing this issue.
          Hide
          Stefan Seelmann added a comment -

          Fixed here: http://svn.apache.org/viewvc?rev=615363&view=rev

          There are still some issues in the Bea LDAP server. For example the schema entry has the following attribute:
          objectclasses: ( 2.5.6.28 NAME 'EProperty' DESC 'This holds the user profile's property.' SUP top MUST cn MAY ( EPfType $ EPfValid $ EPfValue ) )
          Note the quote in the middle of the DESC value. The schema parser fails to parse this objectclass definition.

          Show
          Stefan Seelmann added a comment - Fixed here: http://svn.apache.org/viewvc?rev=615363&view=rev There are still some issues in the Bea LDAP server. For example the schema entry has the following attribute: objectclasses: ( 2.5.6.28 NAME 'EProperty' DESC 'This holds the user profile's property.' SUP top MUST cn MAY ( EPfType $ EPfValid $ EPfValue ) ) Note the quote in the middle of the DESC value. The schema parser fails to parse this objectclass definition.
          Hide
          Stefan Seelmann added a comment -

          I made some test with en BEA embedded LDAP, it seems it isn't fufill the LDAP specs

          When browsing in Studio we are requesting the following attributes: "* objectClass" or "* +"

          According to RFC 4511 section 4.5.1.8. these are correct request:
          ------------------------------------------------------------------------------------------
          2. A list containing "*" (with zero or more attribute
          descriptions) requests the return of all user attributes in
          addition to other listed (operational) attributes.
          ------------------------------------------------------------------------------------------

          However the BEA embedded LDAP only returns all attributes if only "*" is requested.

          If "* objectClass" is requested it doesn't note the "" but only "objectClass". We could optimize that request, it is enought to just ask for "".

          The other request "* " is used to retrieve user attributes as well as operational attributes if the option "Show operational attributes" is enabled. We could also optimize that request, we should only send the "" if the server supports this feature (supportedFeatures=1.3.6.1.4.1.4203.1.5.1).

          Show
          Stefan Seelmann added a comment - I made some test with en BEA embedded LDAP, it seems it isn't fufill the LDAP specs When browsing in Studio we are requesting the following attributes: "* objectClass" or "* +" According to RFC 4511 section 4.5.1.8. these are correct request: ------------------------------------------------------------------------------------------ 2. A list containing "*" (with zero or more attribute descriptions) requests the return of all user attributes in addition to other listed (operational) attributes. ------------------------------------------------------------------------------------------ However the BEA embedded LDAP only returns all attributes if only "*" is requested. If "* objectClass" is requested it doesn't note the " " but only "objectClass". We could optimize that request, it is enought to just ask for " ". The other request "* " is used to retrieve user attributes as well as operational attributes if the option "Show operational attributes" is enabled. We could also optimize that request, we should only send the " " if the server supports this feature (supportedFeatures=1.3.6.1.4.1.4203.1.5.1).
          Hide
          Emmanuel Lecharny added a comment -

          BEA embeded "ldap" is not a real LDAP server, AFAIK. It's a kind of proxy (a VD in fact, part of the Octet-String company BEA bought more than 2 years ago ). I'm afraid that it may cause some difficulties when browsing it with the studio ...

          However, it would be interesting to check the logs on the server to see what is going on.

          Another element would be to give some information about the added attributes, and about the used schema.

          Show
          Emmanuel Lecharny added a comment - BEA embeded "ldap" is not a real LDAP server, AFAIK. It's a kind of proxy (a VD in fact, part of the Octet-String company BEA bought more than 2 years ago ). I'm afraid that it may cause some difficulties when browsing it with the studio ... However, it would be interesting to check the logs on the server to see what is going on. Another element would be to give some information about the added attributes, and about the used schema.

            People

            • Assignee:
              Stefan Seelmann
              Reporter:
              Nicholas Makin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development