Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-428

Same Name for attribute type and objectclass

    Details

      Description

      given a class

      objectclass ( 1.3.6.1.4.1.25977.1.1.1.2.5
      NAME 'racfClass'
      DESC 'Abbildung einer RACF Resourceklasse z.B. G000401'
      SUP RRContainer
      STRUCTURAL
      MUST racfClass
      MAY ( cn $ racfResourceMember )
      )

      and attribute type

      attributetype ( 1.3.6.1.4.1.25977.1.1.1.1.31
      NAME 'racfClass'
      DESC 'racfClass'
      EQUALITY caseIgnoreMatch
      ORDERING caseIgnoreOrderingMatch
      SUBSTR caseIgnoreSubstringsMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
      )

      studio complains about alias already in use by another item ...

      for your investigation my superior class

      objectclass ( 1.3.6.1.4.1.25977.1.1.1.2.1
      NAME 'RRContainer'
      DESC 'Standard Container, erweitert um Beschreibung und Status'
      SUP top
      STRUCTURAL
      MUST cn
      MAY ( description $ rr-status )
      )

      this works under openldap and ldap z/OS

        Issue Links

          Activity

          Pierre-Arnaud Marcelot made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Hide
          Pierre-Arnaud Marcelot added a comment -

          Version 2.0.0 M1 has been released.

          Closing the issue.

          Show
          Pierre-Arnaud Marcelot added a comment - Version 2.0.0 M1 has been released. Closing the issue.
          Pierre-Arnaud Marcelot made changes -
          Fix Version/s 2.0.0-M1 [ 12319458 ]
          Pierre-Arnaud Marcelot made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Hide
          Pierre-Arnaud Marcelot added a comment -

          This is now fixed in trunk.

          Show
          Pierre-Arnaud Marcelot added a comment - This is now fixed in trunk.
          Hide
          Mike Rankin added a comment -

          It looks like their are two instances of this problem in the ds 2m2 release. check out ads-changeLog 1.3.6.1.4.1.18060.0.4.1.3.120 and ads-journal 1.3.6.1.4.1.18060.0.4.1.3.140

          Show
          Mike Rankin added a comment - It looks like their are two instances of this problem in the ds 2m2 release. check out ads-changeLog 1.3.6.1.4.1.18060.0.4.1.3.120 and ads-journal 1.3.6.1.4.1.18060.0.4.1.3.140
          Pierre-Arnaud Marcelot made changes -
          Fix Version/s 2.0.0 [ 12314306 ]
          Stefan Seelmann made changes -
          Field Original Value New Value
          Link This issue is duplicated by DIRSTUDIO-454 [ DIRSTUDIO-454 ]
          Hide
          Gunther Lochstampfer added a comment -

          http://www.ietf.org/rfc/rfc2252.txt says only:

          Schema developers MUST NOT create object class definitions whose
          names conflict with attributes defined for use with LDAP in existing
          standards-track RFCs.

          or

          Schema developers MUST NOT create attribute definitions whose names
          conflict with attributes defined for use with LDAP in existing
          standards-track RFCs.

          but i defined my very own classes and attribute types which do not conflict with standard names ... or OID's

          and this works very fine in openldap and zOS ldap or Tivoly directory, so in my understanding it is a bug

          Show
          Gunther Lochstampfer added a comment - http://www.ietf.org/rfc/rfc2252.txt says only: Schema developers MUST NOT create object class definitions whose names conflict with attributes defined for use with LDAP in existing standards-track RFCs. or Schema developers MUST NOT create attribute definitions whose names conflict with attributes defined for use with LDAP in existing standards-track RFCs. but i defined my very own classes and attribute types which do not conflict with standard names ... or OID's and this works very fine in openldap and zOS ldap or Tivoly directory, so in my understanding it is a bug
          Hide
          Kiran Ayyagari added a comment -

          In the schema no two elements (either attributetype or objectcalss) can have the same name.This is invalid. ( I forgot the rfc number which states this Can someone mention the rfc number which states this.)

          Show
          Kiran Ayyagari added a comment - In the schema no two elements (either attributetype or objectcalss) can have the same name.This is invalid. ( I forgot the rfc number which states this Can someone mention the rfc number which states this.)
          Gunther Lochstampfer created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Gunther Lochstampfer
            • Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development