Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-326

Non-Operational attributes are marked as operational when bind to Siemens DirX 7.0

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.2.0
    • Component/s: studio-ldapbrowser
    • Labels:
      None
    • Environment:
      Client: Windows XP Professional SP2
      Server: Siemens DirX V7.0 B00

      Description

      Non-operational attributes are marked as operational in then entry editor (and are therefor not editable).
      This happens after working with ldapbrowser for some (not reproducible) time.

      1. LDAP Audit ok.txt
        12 kB
        Konrad Ascher-Kyris
      2. LDAP Audit failed.txt
        12 kB
        Konrad Ascher-Kyris
      3. Apache Directory Studio.log
        1 kB
        Konrad Ascher-Kyris

        Issue Links

          Activity

          Hide
          Pierre-Arnaud Marcelot added a comment -

          Apache Directory Studio 1.2.0 has now been released.

          Let's clean Jira and close this issue.

          Show
          Pierre-Arnaud Marcelot added a comment - Apache Directory Studio 1.2.0 has now been released. Let's clean Jira and close this issue.
          Hide
          Stefan Seelmann added a comment -

          Fixed in commit http://svn.apache.org/viewcvs?view=rev&rev=663698

          Changed the way how the schema is loaded.

          Show
          Stefan Seelmann added a comment - Fixed in commit http://svn.apache.org/viewcvs?view=rev&rev=663698 Changed the way how the schema is loaded.
          Hide
          Stefan Seelmann added a comment -

          Thanks Konrad for the logs.

          Show
          Stefan Seelmann added a comment - Thanks Konrad for the logs.
          Hide
          Konrad Ascher-Kyris added a comment -

          .log and LDAP audits

          Show
          Konrad Ascher-Kyris added a comment - .log and LDAP audits
          Hide
          Konrad Ascher-Kyris added a comment -

          Hi Stefan,

          I did some more testing and could reproduce the following effects:

          • after opening a connection for the first time (manually or automatically) there is an error "Missing schema location in RootDSE, using default schema." (see attached .log). In this case all non-standard attributes are marked as operational.
          • after disconnecting and connecting again the schema is read successfully

          I examined the ldap audits and found a difference in the operation where the schema is read (complete audit files attached):

          Failed operation:

          Operation :SEARCH
          Version :3
          MessageID :14
          Base Obj :cn=schema
          Scope :baselevel
          Filter :(objectClass=subschema)
          Size Limit :0
          Time Limit :0
          Deref Alias :always
          Types Only :no
          Req Attr # :3
          Req Attr :createTimestamp
          Req Attr :modifyTimestamp
          Req Attr :objectClass
          Found Entries :1
          Found Attrs :1
          Found Values :3
          Bytes Received :108
          Bytes Returned :135
          Cached Result :no
          Abandoned :no
          Result Code :0 (success)

          OK operation:
          ----------------- OPERATION 000015 ----------------
          Operation :SEARCH
          Version :3
          MessageID :14
          Base Obj :cn=schema
          Scope :baselevel
          Filter :(objectClass=subschema)
          Size Limit :0
          Time Limit :0
          Deref Alias :always
          Types Only :no
          Req Attr # :7
          Req Attr :objectClasses
          Req Attr :attributeTypes
          Req Attr :ldapSyntaxes
          Req Attr :matchingRules
          Req Attr :matchingRuleUse
          Req Attr :createTimestamp
          Req Attr :modifyTimestamp
          Found Entries :1
          Found Attrs :2
          Found Values :2143
          Bytes Received :174
          Bytes Returned :417864
          Cached Result :no
          Abandoned :no
          Result Code :0 (success)

          Show
          Konrad Ascher-Kyris added a comment - Hi Stefan, I did some more testing and could reproduce the following effects: after opening a connection for the first time (manually or automatically) there is an error "Missing schema location in RootDSE, using default schema." (see attached .log). In this case all non-standard attributes are marked as operational. after disconnecting and connecting again the schema is read successfully I examined the ldap audits and found a difference in the operation where the schema is read (complete audit files attached): Failed operation: Operation :SEARCH Version :3 MessageID :14 Base Obj :cn=schema Scope :baselevel Filter :(objectClass=subschema) Size Limit :0 Time Limit :0 Deref Alias :always Types Only :no Req Attr # :3 Req Attr :createTimestamp Req Attr :modifyTimestamp Req Attr :objectClass Found Entries :1 Found Attrs :1 Found Values :3 Bytes Received :108 Bytes Returned :135 Cached Result :no Abandoned :no Result Code :0 (success) OK operation: ----------------- OPERATION 000015 ---------------- Operation :SEARCH Version :3 MessageID :14 Base Obj :cn=schema Scope :baselevel Filter :(objectClass=subschema) Size Limit :0 Time Limit :0 Deref Alias :always Types Only :no Req Attr # :7 Req Attr :objectClasses Req Attr :attributeTypes Req Attr :ldapSyntaxes Req Attr :matchingRules Req Attr :matchingRuleUse Req Attr :createTimestamp Req Attr :modifyTimestamp Found Entries :1 Found Attrs :2 Found Values :2143 Bytes Received :174 Bytes Returned :417864 Cached Result :no Abandoned :no Result Code :0 (success)
          Hide
          Stefan Seelmann added a comment -

          Hi Konrad,

          does that mean, it works for some time and suddenly the non-operational attributes become uneditable? Are there any error messages poping up? Could you please check your ~/.ApacheDirectoryStudio/.metadata/.log file for error messages? Could you try to close and open the connection, does the problem disappear then?

          I tested against DirX6 and there were some issues. Do you think it is possible for us to get an DirX7 installation for testing? Or could you provide us an installation available via Internet?

          Regards,
          Stefan

          Show
          Stefan Seelmann added a comment - Hi Konrad, does that mean, it works for some time and suddenly the non-operational attributes become uneditable? Are there any error messages poping up? Could you please check your ~/.ApacheDirectoryStudio/.metadata/.log file for error messages? Could you try to close and open the connection, does the problem disappear then? I tested against DirX6 and there were some issues. Do you think it is possible for us to get an DirX7 installation for testing? Or could you provide us an installation available via Internet? Regards, Stefan
          Hide
          Konrad Ascher-Kyris added a comment -

          this is still an issui in V 1.1.0

          Show
          Konrad Ascher-Kyris added a comment - this is still an issui in V 1.1.0

            People

            • Assignee:
              Stefan Seelmann
              Reporter:
              Konrad Ascher-Kyris
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development