Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-99

Display both OID and text for controls etc. in the property page of the Root DSE

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      LDAP Studio 0.8.0

      Description

      Currently, LDAP Studio displays either the OID of a supported LDAP control in the property page, or a text (if the OID is known to LS). See screenshoot for an example. I would prefer if both the OID and the description are shown, because the OID makes a good search term for Google etc. if someone tries to find out more about it. The same holds true for LDAP extended operations and features.

      Idea: Possible solutions would be using the forms

      1.2.840.113556.1.4.805 (Tree Delete)

      or

      Tree Delete (1.2.840.113556.1.4.805)

      if control (feature ...) known.

      1. screenshot-1.jpg
        49 kB
        Stefan Zoerner

        Activity

        Hide
        Stefan Zoerner added a comment -

        Example: Supported controls by IBM TivoliDS 6.0 (some are known to LS, some are not)

        Show
        Stefan Zoerner added a comment - Example: Supported controls by IBM TivoliDS 6.0 (some are known to LS, some are not)
        Hide
        Stefan Seelmann added a comment -

        One more suggestion: We could create a value editor for supportedControls, supportedExtensions and supportedFeatures or more general for the OID syntax 1.3.6.1.4.1.1466.115.121.1.38. It just has to decorate the OID string with the description. The implemention could be similar to the o.a.d.l.valueeditors.time.InPlaceGeneralizedTimeValueEditor value editor. With such an value editor the OIDs and their corresponding description could just be displayed within the EntryEditor.

        To translate the OIDs to their description a lookup table would be great. Or is there already some kind of OID-to-description registry in ldap-shared?

        Show
        Stefan Seelmann added a comment - One more suggestion: We could create a value editor for supportedControls, supportedExtensions and supportedFeatures or more general for the OID syntax 1.3.6.1.4.1.1466.115.121.1.38. It just has to decorate the OID string with the description. The implemention could be similar to the o.a.d.l.valueeditors.time.InPlaceGeneralizedTimeValueEditor value editor. With such an value editor the OIDs and their corresponding description could just be displayed within the EntryEditor. To translate the OIDs to their description a lookup table would be great. Or is there already some kind of OID-to-description registry in ldap-shared?
        Hide
        Stefan Zoerner added a comment -

        Maybe just a temporary solution, but I have implemented this in the form
        OID (description)
        with this commit
        http://svn.apache.org/viewvc?view=rev&revision=537156

        Show
        Stefan Zoerner added a comment - Maybe just a temporary solution, but I have implemented this in the form OID (description) with this commit http://svn.apache.org/viewvc?view=rev&revision=537156

          People

          • Assignee:
            Stefan Zoerner
            Reporter:
            Stefan Zoerner
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development