Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

More documents

Recommendations

Info

Single-Valued versus Multivalued An attribute defaults to multivalued unless it is explicitly made single-valued. The following example LDIF file makes title single-valued by adding the SINGLE-VALUE keyword after the SYNTAX section: 1 version: 1 2 dn: cn=schema 3 changetype: add 4 attributeTypes: ( 2.5.4.12 NAME ’title’ DESC ’Standa 5 rd Attribute’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{ 6 64} SINGLE-VALUE X-NDS_NAME ’Title’ X-NDS_NOT_SCHED 7 _SYNC_IMMEDIATE ’1’ X-NDS_LOWER_BOUND ’1’) 8 novdocx (ENU) 01 February 2006 Adding an Optional Attribute to an Existing Object Class Although adding new schema elements is an acceptable practice, modifying or extending existing schema elements is usually dangerous. Because every schema element is uniquely identified by an OID, when you extend a standard schema element, you effectively create a second definition for the element even though it still uses the original OID. This can cause incompatibility problems. There are times when it is appropriate to change schema elements. For example, you might need to extend or modify new schema elements as you refine them during development. Instead of adding new attributes directly to a class, you should generally use auxiliary classes only to • Add new attributes to an existing object class. • Subclass an existing object class. 5.3.3 Adding or Removing Auxiliary Classes The following sample LDIF file creates two new attributes, creates an auxiliary class with these new attributes, then adds an inetOrgPerson entry with the auxiliary class as an object class of the entry and with values for the auxiliary class attributes. version: 1 # Add an attribute to track a bear’s hair. The attribute is # multi-valued, uses a case ignore string syntax, # and has public read rights # Values may include: long hair, short, curly, straight, # none, black, and brown # X-NDS_PUBLIC_READ ’1’ The 1 allows public read, # 0 denies public read dn: cn=schema changetype: modify add: attributeTypes attributeTypes: ( 2.16.840.1.113719.1.186.4.10 NAME ’bearHair’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-NDS_PUBLIC_READ ’1’ ) # add an attribute to store a bear’s picture dn: cn=schema changetype: modify add: attributeTypes 36 Novell eDirectory 8.8 Troubleshooting Guide
attributeTypes: ( 2.16.840.1.113719.1.186.4.11 NAME ’bearPicture’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 SINGLE-VALUE ) # create an Auxiliary class for the bearfeatures dn: cn=schema changetype: modify add: objectclasses objectclasses: (2.16.840.1.113719.1.186.6.101 NAME ’bearFeatures’ MAY (bearHair $ bearPicture) AUXILIARY) novdocx (ENU) 01 February 2006 # now create a user named bobby dn: cn=bobby,o=bearcave changetype: add cn: bobby sn: bear givenName: bobby bearHair: Short bearHair: Brown bearHair: Curly bearPicture:< file:///c:/tmp/alien.jpg objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: bearFeatures # now create a person named john that will later be changed # into a bear when bearFeatures is added to its objectClass # list dn: cn=john,o=bearcave changetype: add cn: John sn: bear givenName: john objectClass: top objectClass: person objectClass: inetOrgPerson # now morph john into a bear by adding bearFeatures dn: cn=john,o=bearcave changetype: modify add: objectClass objectClass: bearFeatures - add: bearHair bearHair: long bearHair: black #bearPicture:< file:///c:/tmp/john.jpg> - # to morph john back to a person, simply delete the # objectClass bearFeatures dn: cn=john,o=bearcave changetype: modify Troubleshooting LDIF Files 37
Page 1 and 2: Novell eDirectory 8.8 Troubleshooti
Page 3 and 4: Novell Trademarks Client32 is a tra
Page 5 and 6: About This Book This Installation G
Page 7 and 8: 1Resolving Error Codes For a comple
Page 9 and 10: 2Installation and Configuration •
Page 11 and 12: 4c Edit the /etc/slpuasa.conf to ad
Page 13 and 14: 3Determining the eDirectory Version
Page 15 and 16: • Run iMonitor. On the Agent Summ
Page 17 and 18: On the Agent Summary page, click Kn
Page 19 and 20: 4Log Files This section contains in
Page 21 and 22: 5Troubleshooting LDIF Files The Nov
Page 23 and 24: Component Record Delimiters Descrip
Page 25 and 26: 14 changetype: delete 15 The Modify
Page 27 and 28: Field newsuperior (optional) Descri
Page 29 and 30: Example 3 For Digest MD5 hashed pas
Page 31 and 32: Option User DN Password Description
Page 33 and 34: You can use this file to examine or
Page 35: Containment Rules The object classe
Page 39 and 40: 6Troubleshooting SNMP This section
Page 41 and 42: For any problem configuring the eDi
Page 43 and 44: 7Obituaries There has been a great
Page 45 and 46: If the obituary is a Primary obitua
Page 47 and 48: • Obituaries can change states on
Page 49 and 50: 8Migrating to Novell eDirectory Thi
Page 51 and 52: delete : objectclasses objectclasse
Page 53 and 54: - add: objectclasses objectclasses:
Page 55 and 56: Step 2: Rectify the Error LDIF File
Page 57 and 58: 9Replication • Section 9.1, “Re
Page 59 and 60: 10Novell Public Key Infrastructure
Page 61 and 62: 1Troubleshooting Utilities on Linux
Page 63 and 64: Option Description -P Replica and P
Page 65 and 66: Option Optional Schema Enhancements
Page 67 and 68: a replica on the partition is synch
Page 69 and 70: 11.6 Using ndstrace The ndstrace ut
Page 71 and 72: Trace Flag FRAG IN INIT INSP Descri
Page 73 and 74: Trace Flag Parameters Description *
Page 75 and 76: Trace Flag Parameters Description *
Page 77 and 78: 12NMAS on Linux and UNIX • Sectio
Page 79 and 80: 13Troubleshooting on Windows • Se
Page 81 and 82: 14Accessing HTTPSTK When DS Is Not
Page 83 and 84: 15Encrypting Data in eDirectory In
Page 85 and 86: OR 2. Disable ER at the parent or c
Page 87 and 88:
16The eDirectory Management Toolbox
Page 89 and 90:
17SASL-GSSAPI This section discusse
Page 91 and 92:
18Miscellaneous • Section 18.1,
show all

Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

Create successful ePaper yourself

Delete template?

Save as template?