 |
Configuration,
Command, and File Reference Netscape Directory Server |
| Previous |
Contents |
Index |
DocHome | Next |
This chapter contains reference information on Netscape Directory Server (Directory Server) server plug-ins. The chapter is divided into the following sections:
The configuration for each part of Directory Server plug-in functionality has its own separate entry and set of attributes under the subtree cn=plugins,cn=config. Code Example 2-2, which you saw in chapter 2, "Core Server Configuration Reference," shows some of the plug-in configuration attributes.
|
|
|
dn: cn=Telephone
Syntax,cn=plugins,cn=config |
|
|
Some of these attributes are common to all plug-ins while others may be particular to a specific plug-in. You can check which attributes are currently being used by a given plug-in by performing an ldapsearch on the cn=config subtree.
All plug-ins are instances of the nsSlapdPlugin object class, which in turn inherits from the extensibleObject object class. For plug-in configuration attributes to be taken into account by the server, both of these object classes (in addition to the top object class) must be present in the entry, as shown in the following example:
|
|
|
dn:cn=ACL
Plugin,cn=plugins,cn=config |
|
|
The tables that follow provide you with a quick overview of the plug-ins provided with Directory Server, along with their configurable options, configurable arguments, default setting, dependencies, general performance related information, and further reading. Information in these tables will help you to weigh plug-in performance gains and costs and choose the optimal settings for your deployment. The "Further Information" row cross references further reading where this is available.
|
Chapter 6, "Managing Access Control," in the Netscape Directory Server Administrator's Guide. |
|
Chapter 6, "Managing Access Control," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
Chapter 3, "Configuring Directory Databases," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
Chapter 5, "Advanced Entry Management," in the Netscape Directory Server Administrator's Guide. |
|
The Internationalization has one argument, which must not be modified: serverRoot/slapd-serverID/config/slapd-collations.conf This directory stores the collation orders and locale s used by the internationalization plug-in. |
|
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
See Appendix D, "Internationalization," in the Netscape Directory Server Administrator's Guide. |
|
See Database Plug-in Attributes for further information on database configuration. |
|
|
Chapter 3, "Configuring Directory Databases," in the Netscape Directory Server Administrator's Guide. |
|
Enables a current version Directory Server to be a consumer of a 4.x supplier |
|
|
None. This plug-in can be disabled if the server is not (and never will be) a consumer of a 4.x server. |
|
|
Chapter 8, "Managing Replication," in the Netscape Directory Server Administrator's Guide. |
|
You can turn this plug-in off if you only have one server which will never replicate. See also chapter 8, "Managinng Replication," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
Chapter 7, "User Account Management," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
Chapter 7, "User Account Management," in the Netscape Directory Server Administrator's Guide. |
|
cn=NS-MTA-MD5,cn=Password Storage Schemes,cn=plugins,cn=config |
|
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
You can no longer choose to encrypt passwords using the NS-MTA-MD5 password storage scheme. The storage scheme is still present but only for reasons of backward compatibility; i.e. if the data in your directory still contains passwords encrypted with the NS-MTA-MD5 password storage scheme. See chapter 7, "User Account Management," in the Netscape Directory Server Administrator's Guide. |
|
If there are not passwords encrypted using the SHA password storage scheme, you may turn this plug-in off. If you want to encrypt your password with the SHA password storage scheme, we recommend that you choose SSHA instead, as SSHA is a far more secure option. |
|
|
Chapter 7, "User Account Management," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
Chapter 7, "User Account Management," in the Netscape Directory Server Administrator's Guide. |
|
Chapter 18, "Configuring IM Presence Informtion," in the Netscape Directory Server Administrator's Guide. |
|
Enables pass-through authentication, the mechanism which allows one directory to consult another to authenticate bind requests. |
|
|
Chapter 16, "Using the Pass-though Authentication Plug-in," in the Netscape Directory Server Administrator's Guide. |
|
When enabled, the post operation Referential Integrity plug-in performs integrity updates on the member, uniquemember, owner, and seeAlso attributes immediately after a delete or rename operation. You can reconfigure the plug-in to perform integrity checks on all other attributes. Configurable arguments are as follows:
|
|
|
You should enable the Referential Integrity plug-in on only one supplier in a multi-master replication environment to avoid conflict resolution loops. When enabling the plug-in on chained servers, you must be sure to analyze your performance resource and time needs as well as your integrity needs. Note that integrity checks can be time-consuming and draining on memory/CPU. |
|
|
See chapter 3, "Configuring Directory Databases," in the Netscape Directory Server Administrator's Guide. |
|
Used by LDAP clients for maintaining application compatibility with Directory Server 4.x versions. Maintains a log of all changes occurring in the Directory Server. The Retro Changelog offers the same functionality as the changelog in the 4.x versions of Directory Server. |
|
|
See Retro Changelog Plug-in Attributes for further information on the two configuration attributes for this plug-in. |
|
|
Chapter 8, "Managing Replication," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
Chapter 5, "Advanced Entry Management," in the Netscape Directory Server Administrator's Guide. |
|
Do not modify the configuration of this plug-in. It is recommended that you leave this plug-in running at all times. |
|
|
This plug-in enables the Directory Server to support space and case insensitive values. Applications can now search the directory using entries with ASCII space characters. For example, applications that use AOL Screen Names can search the Directory Server using filters that contain Screen Names--a search or compare operation that uses jOHN Doe will match entries that contain any of the following Screen Name values: johndoe, john doe, and John Doe. For more information about finding directory entries, see Appendix B, "Finding Directory Entries," in the Netscape Directory Server Administrator's Guide. The nsAIMID attribute type, which is a part of the Presence schema, uses this syntax. For details, see "Schema for the Presence Plug-in" in the Netscape Directory Server Administrator's Guide. |
|
Checks that the values of specified attributes are unique each time a modification occurs on an entry. |
|
|
Enter the following arguments: if you want to check for UID attribute uniqueness in all listed subtrees. However, enter the following arguments: attribute="uid" requiredObjectClass= "ObjectClassName" if you want to check for UID attribute uniqueness when adding or updating entries with the requiredObjectClass, starting from the parent entry containing the ObjectClass as defined by the MarkerObjectClass attribute. |
|
|
Directory Server provides the UID Uniqueness plug-in by default. If you want to ensure unique values for other attributes, you can create instances of the UID Uniqueness plug-in for those attributes. See chapter 17, "Using the Attribute Uniqueness Plug-in," in the Netscape Directory Server Administrator's Guide for more information about the Attribute Uniquenss plug-in. The UID Uniqueness plug-in is off by default due to operation restrictions that need to be addressed before enabling the plug-in in a multi-master replication environment. Turning the plug-in on may slow down Directory Server performance. |
|
|
Chapter 17, "Using the Attribute Uniqueness Plug-in," in the Netscape Directory Server Administrator's Guide. |