Red Hat DIRECTORY SERVER 7.1 SP7 - S Anleitung zur Fehlerbehebung PDF herunterladen (Seite 34)

34 Novell eDirectory 8.8 SP7 Troubleshooting Guide

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

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.

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

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

If you have problems with an LDIF file, consider the following:

1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 119 120

Keine Kommentare

Red Hat DIRECTORY SERVER 7.1 SP7 - S Anleitung zur Fehlerbehebung Seite 34