base Attributes under cn=attributeName, cn=encrypted attributes, cn=database_name, cn=ldbm database, cn=plugins, cn=config191would not be. Indexed searches are significantly faster than unindexed searches, so changing theminimum length of the search key is helpful to increase the number of indexed searches.This substring length can be edited based on the position of any wildcard characters. ThensSubStrMiddle attribute sets the required number of characters for an indexed search where awildcard is used in the middle of a search string. For example:ab*zIf the value of this attribute is changed, then the index must be regenerated using db2index.Parameter DescriptionEntry DN cn=attribute_name, cn=index,cn=database_name, cn=ldbm database,cn=plugins, cn=configValid Values Any integerDefault Value 3Syntax IntegerExample nsSubStrMiddle: 33.4.8. Database Attributes under cn=attributeName, cn=encryptedattributes, cn=database_name, cn=ldbm database, cn=plugins,cn=configThe nsAttributeEncryption object class allows selective encryption of attributes within adatabase. Extremely sensitive information such as credit card numbers and government identificationnumbers may not be protected enough by routine access control measures. Normally, these attributevalues are stored in CLEAR within the database; encrypting them while they are stored adds anotherlayer of protection. This object class has one attribute, nsEncryptionAlgorithm, which sets theencryption cipher used per attribute. Each encrypted attribute represents a subentry under the abovecn=config information tree nodes, as shown in the following diagram:Figure 3.3. Encrypted Attributes under the cn=config NodeFor example, the database encryption file for the userPassword attribute under o=UserRootappears in the Directory Server as follows:
