![]() |
Schema
Reference Guide Netscape Directory Server |
| Previous |
Contents |
Index |
DocHome | Next |
This chapter provides definitions, syntax, and OIDs used by Netscape Directory Server (Directory Server). Operational attributes are available for use on every entry in the directory, regardless of whether they are defined for the object class of the entry. Operational attributes are only returned in an ldapsearch operation if specifically requested. This chapter also provides definitions, syntax, and OIDs for some special attributes and object classes that are used by the server. (When an object class inherits attributes from other object classes, the inherited attributes are shown in italics.) The attributes are listed by section, then alphabetically.
The values of this attribute are URLs of other servers which may be contacted when this server becomes unavailable. If the server does not know of any other servers which could be used, this attribute is absent. You may cache this information in case your preferred LDAP server later becomes unavailable.
Corresponds to a naming context the server is mastering or shadowing. When the Directory Server does not master any information (such as when it is an LDAP gateway to a public X.500 directory), this attribute is absent. When the Directory Server believes it contains the entire directory, the attribute has a single value and that value is the empty string (indicating the null DN of the root).This attribute permits a client contacting a server to choose suitable base objects for searching.
This attribute contains the distinguished name of all roles that apply to an entry. Membership of a managed role is conferred upon an entry by adding the role's DN to the entry's nsRoleDN attribute.
dn:
cn=staff,o=Netscape,o=example.com
objectclass:
LDAPsubentry
objectclass:
nsRoleDefinition
objectclass:
nsSimpleRoleDefinition
objectclass:
nsManagedRoleDefinition
dn: cn=userA,ou=users,o=Netscape,o=example.com
objectclass: top
objectclass: person
sn: uA
userpassword: secret
nsroledn: cn=staff,o=Netscape,o=example.com
A nested role specifies containment of one or more roles of any type. In that case, nsRoleDN defines the DN of the contained roles.
dn:
cn=everybody,o=Netscape,o=example.com
objectclass:
LDAPsubentry
objectclass:
nsRoleDefinition
objectclass:
nsComplexRoleDefinition
objectclass:
nsNestedRoleDefinition
nsroledn:
cn=manager,o=Netscape,o=example.com
nsroledn:
cn=staff,o=Netscape,o=example.com
Specifies whether the password syntax will be checked before the password is saved. (The password syntax checking mechanism checks that the password meets or exceeds the password minimum length requirement and that the string does not contain any trivial words, such as the user's name or ID or any attribute value stored in the uid, cn, sn, givenName, ou, or mail attributes of the user's directory entry.)
This attribute is defined in Directory Server.
Indicates whether user passwords will expire after a given number of seconds. By default, user passwords do not expire. Once password expiration is enabled, you can set the number of seconds after which the password will expire using the passwordMaxAge (pwdMaxAge) attribute.
Indicates the number of passwords the Directory Server stores in history. Passwords that are stored in history cannot be reused by users. By default, the password history feature is disabled. That is, the Directory Server does not store any old passwords, so users can reuse passwords. You can enable password history by using the passwordInHistory (pwdInHistory) attribute.
To prevent users from rapidly cycling through the number of passwords that you are tracking, use the passwordMinAge attribute.
This attribute is defined in Directory Server.
Indicates whether users will be locked out of the directory after a given number of failed bind attempts. By default, users will not be locked out of the directory after a series of failed bind attempts. If you enable account lockout, you can set the number of failed bind attempts after which the user will be locked out using the passwordMaxFailure (pwdMaxFailure) attribute.
Indicates the amount of time in seconds during which users will be locked out of the directory after an account lockout. The account lockout feature protects against hackers who try to break into the directory by repeatedly trying to guess a user's password. You enable and disable the account lockout feature using the passwordLockout (pwdLockOut) attribute.
Indicates the number of seconds after which user passwords will expire. To use this attribute, you must enable password expiration using the passwordExp attribute.
Indicates the number of failed bind attempts after which a user will be locked out of the directory. By default, account lockout is disabled. You can enable account lockout by modifying the passwordLockout (pwdLockOut) attribute.
Indicates the number of seconds that must pass before a user can change his password. Use this attribute in conjunction with the passwordInHistory (pwdInHistory) attribute to prevent users from quickly cycling through passwords so that they can use their old password again. A value of zero (0) indicates that the user can change the password immediately.
Specifies the minimum number of characters that must be used in Directory Server user password attributes. In general, shorter passwords are easier to crack, so you are recommended to set a password length of at least 6 or 7 characters. This is long enough to be difficult to crack, but short enough that users can remember the password without writing it down.
Indicates the amount of time in seconds after which the password failure counter will be reset. Each time an invalid password is sent from the user's account, the password failure counter is incremented. If the passwordLockout (pwdLockOut) attribute is set to on, users will be locked out of the directory when the counter reaches the number of failures specified by the passwordMaxFailure (pwdMaxFailure) attribute (within 600 seconds by default). After the amount of time specified by the passwordLockoutDuration (pwdLockoutDuration) attribute, the failure counter is reset to zero (0).
Specifies the type of encryption used to store Directory Server passwords. Entering the password in CLEAR for this attribute indicates that the password will appear in plain text.
The following encryption types are supported by Directory Server:
Indicates whether users will be locked out of the directory for a specified amount of time or until the administrator resets the password after an account lockout. The account lockout feature protects against hackers who try to break into the directory by repeatedly trying to guess a user's password. If this passwordUnlock attribute is set to off and the operational attribute accountUnlockTime has a value of 0, then the account will be locked indefinitely.
Indicates lengh of time in seconds before a user's password expires that the user will receive a password expiration warning. The warning control will appear on their next LDAP operation. Depending on the LDAP client, the user may also be prompted to change their password at the time the warning is sent.
Specifies the length of time that passes before the passwordRetryCount is reset.
Identifies the encryption cipher for the encrypted attribute(s) in the nsAttributeEncryption object class.
Contains a regular expression used to map SASL
identity strings.
This attribute is defined in Directory Server.
Case-Exact String, single-valued
2.16.840.1.113730.3.1.2064
Contains the search base DN template used in SASL
identity mapping.
This attribute is defined in Directory Server.
Case-Exact String, single-valued
2.16.840.1.113730.3.1.2065
Contains the search filter template used in SASL
identity mapping.
This attribute is defined in Directory Server.
Case-Exact String, single-valued
2.16.840.1.113730.3.1.2066
Used to represent changes made to the Directory Server. You can configure Directory Server to maintain a change log that is compatible with the change log implemented in Directory Server 4.1x by enabling the Retro Change Log Plug-in. Each entry in the change log has the object class changeLogEntry.
An auxilary object class subentry used to administer the subschema for the subschema administrative area. It holds the operational attributes representing the policy parameters used to express the subschema.
| Previous |
Contents |
Index |
DocHome | Next |