Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

More documents

Recommendations

Info

5.1.4 Line Folding within LDIF Files To fold a line in an LDIF file, simply insert a line separator (a newline or a carriage return/newline pair) followed by a space at the place where you want the line folded. When the LDIF parser encounters a space at a beginning of the line, it knows to concatenate the rest of the data on the line with the data on the previous line. The leading space is then discarded. novdocx (en) 22 June 2009 You should not fold lines in the middle of a multibyte UTF-8 character. The following is an example of an LDIF file with a folded line (see lines 13 and 14): 1 version: 1 2 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 3 sn: Michaels 4 givenname: Peter 5 objectClass: top 6 objectClass: person 7 objectClass: organizationalPerson 8 objectClass: iNetOrgPerson 9 telephonenumber: +1 415 555 0001 10 mail: Peter.Michaels@aaa.com 11 userpassword: Peter123 12 description: Peter is one of the most popular music 13 ians recording on our label. He’s a big concert dr 14 aw, and his fans adore him. 15 5.1.5 Hashed Password Representation in LDIF Files The hashed password is represented as base64 data in the LDIF file. The attribute name userpassword should be followed with the name of the encryption used for hashing the password. This name should be given within a pair of flower brackets “{ }” as shown below: Example 1 For SHA hashed passwords: 1 version: 1 2 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 3 sn: Michaels 4 userpassword: {SHA}xcbdh46ngh37jsd0naSFDedjAS30dm5 objectclass: inetOrgPerson Example 2 For SSHA hashed passwords: 1 version: 1 2 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 3 sn: Michaels 4 userpassword: {SSHA}sGs948DFGkakdfkasdDF34DF4dS3skl5DFS5 objectclass: inetOrgPerson Example 3 For Digest MD5 hashed passwords: 1 version: 1 2 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 3 sn: Michaels 4 userpassword: {MD5}a45lkSDF234SDFG62dsfsf2DG2QEvgdmnk4305 objectclass: inetOrgPerson 34 Novell eDirectory 8.8 Troubleshooting Guide
5.2 Debugging LDIF Files • “Enabling Forward References” on page 35 • “Checking the Syntax of LDIF Files” on page 37 • “Using the LDIF Error File” on page 38 • “Using LDAP SDK Debugging Flags” on page 39 novdocx (en) 22 June 2009 If you have problems with an LDIF file, consider the following: 5.2.1 Enabling Forward References You might occasionally encounter LDIF files in which a record to add one entry comes before a record to add its parents. When this happens, an error is generated because the new entry’s parent does not exist when the LDAP server attempts to add the entry. To solve this problem, simply enable the use of forward references. When you enable the creation of forward references and an entry is going to be created before its parent exists, a placeholder called a forward reference is created for the entry’s parent to allow the entry to be successfully created. If a later operation creates the parent, the forward reference is changed into a normal entry. It is possible that one or more forward references will remain after your LDIF import is complete (if, for example, the LDIF file never created the parent for an entry). In this case, the forward reference will appear as an Unknown object in ConsoleOne and iManager. Although you can search on a forward reference entry, you cannot read attributes (except objectClass) from the forward reference entry because it does not have any attributes or attribute values. However, all LDAP operations will work normally on the real object entries located below the forward reference. Identifying Forward Reference Entries Forward reference entries have an object class of Unknown and also have their internal NDS EF_REFERENCE entry flag set. In ConsoleOne and iManager, entries with an object class of Unknown are represented by a round yellow icon with a question mark in the center. You can use LDAP to search for objects with an Unknown object class, although there is currently no way to access the entry flag settings through LDAP to be sure that they are forward reference entries. Changing Forward Reference Entries into Normal Objects You can change a forward reference entry into an normal object by simply creating it (using, for example, an LDIF file or an LDAP client request). When you ask eDirectory to create an entry that already exists as a forward reference, eDirectory transforms the existing forward reference entry into the object you asked it to create. Using the Novell eDirectory Import Convert Export Wizard To enable forward references during an LDIF import: 1 In Novell iManager, click the Roles and Tasks button . 2 Click eDirectory Maintenance > Import Convert Export Wizard. 3 Click Import Data from File on Disk, then click Next. 4 Select LDIF as the type of file you want to import. Troubleshooting LDIF Files 35
Page 1 and 2: Troubleshooting Guide AUTHORIZED DO
Page 3 and 4: Novell Trademarks Client32 is a tra
Page 5 and 6: Contents About This Book 11 novdocx
Page 7 and 8: 10.2.1 Step 1: Perform the Schema C
Page 9 and 10: 23.7.3 On Windows . . . . . . . . .
Page 11 and 12: About This Book This Troubleshootin
Page 13 and 14: 1Resolving Error Codes For a comple
Page 15 and 16: 2Installation and Configuration •
Page 17 and 18: 4c Edit the /etc/slpuasa.conf to ad
Page 19 and 20: pkgadd -d NOVLniu0.pkg 4 Start eDir
Page 21 and 22: 3Determining the eDirectory Version
Page 23 and 24: • Run iMonitor. On the Agent Summ
Page 25 and 26: 4Log Files This section contains in
Page 27 and 28: 5Troubleshooting LDIF Files The Nov
Page 29 and 30: Component Record Delimiters Descrip
Page 31 and 32: The Modify Change Type The modify c
Page 33: Field newsuperior (optional) Descri
Page 37 and 38: Option Base DN Scope Description Ba
Page 39 and 40: Using the Novell Import Conversion
Page 41 and 42: 5.3.2 Adding a New Attribute To add
Page 43 and 44: objectclasses: (2.16.840.1.113719.1
Page 45 and 46: 6Troubleshooting SNMP This section
Page 47 and 48: SERVER test-server test-server is t
Page 49 and 50: 7iMonitor • Section 7.1, “Brows
Page 51 and 52: 8iManager • Section 8.1, “LDAP
Page 53 and 54: 9Obituaries There has been a great
Page 55 and 56: If the obituary is a Primary obitua
Page 57 and 58: • Obituaries can change states on
Page 59 and 60: 10Migrating to Novell eDirectory Th
Page 61 and 62: Option 3: Add cn to the definition
Page 63 and 64: changetype: modify delete: objectcl
Page 65 and 66: Any records that contain references
Page 67 and 68: 1Schema This section includes infor
Page 69 and 70: 12ndsrepair • Section 12.1, “Ru
Page 71 and 72: 13Replication • Section 13.1, “
Page 73 and 74: 14Clone DIB Issues • Section 14.1
Page 75 and 76: 15Novell Public Key Infrastructure
Page 77 and 78: 16Troubleshooting Utilities on Linu
Page 79 and 80: Option Description -P Replica and P
Page 81 and 82: Option Optional Schema Enhancements
Page 83 and 84: Determines the complete synchroniza
Page 85 and 86:
16.5.2 Troubleshooting ndsrepair Er
Page 87 and 88:
Trace Flag DNS DRLK DVRS Descriptio
Page 89 and 90:
Trace Flag Parameters Description *
Page 91 and 92:
Trace Flag Parameters Description !
Page 93 and 94:
17NMAS on Linux and UNIX • Sectio
Page 95 and 96:
18Troubleshooting on Windows • Se
Page 97 and 98:
19Accessing HTTPSTK When DS Is Not
Page 99 and 100:
20Encrypting Data in eDirectory In
Page 101 and 102:
Action 1. Upgrade the server to a c
Page 103 and 104:
21The eDirectory Management Toolbox
Page 105 and 106:
2SASL-GSSAPI This section discusses
Page 107 and 108:
Action: Do the following: 1 Update
Page 109 and 110:
23Miscellaneous • Section 23.1,
Page 111 and 112:
These parameters are available in /
Page 113 and 114:
23.7.3 On Windows 1 Go to the novel
Page 115 and 116:
23.19 ndsd Not Listening at the Loo
show all

Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?