If you are using a special LDAP application or end device, which does not immediately work with the default settings, several options are available for adjusting the server to this issue. Normally, this occurs when your LDAP system is searching for certain attributes that are not known to the LDAP server or waiting for certain attributes in the result that will not be supplied. The objectClasses expected by your application, but not supplied by estos MetaDirectory, may also be an additional problem.
Configuration files with the .termxml extension in the config/default under the installation directory are the starting point for making adjustments. You can set attribute assignments for the LDAP server attributes in these files. By default, estos MetaDirectory only knows the LDAP attributes stored in the schema. You can rename these attributes in the assignments.
If your LDAP application is searching for, or filtering, special attributes in estos MetaDirectory, you can assign these attributes to the attributes used by estos MetaDirectory. The attributes supplied can also be renamed.
The assignment file will be divided into three areas in the XML file:
<QueryFilterMapping> <String Key="SAMAccountName">displayName</String> </QueryFilterMapping> <QueryAttributeMapping> <String Key="SAMAccountName">displayName</String> </QueryAttributeMapping> <ResultAttributeMapping> <String Key="displayName">SAMAccountName</String> </ResultAttributeMapping>
The SAMAccountName transferred from you application will be assigned to the displayName for the request and the filter attributes, which will be used for searching and filtering. In turn, the displayName attribute will be assigned to SAMAccountName in the result.
The search filter values can be manipulated with the help of regular expressions. To do this, the assigned fields in the query filter must be extended by using the regsearch and regreplace attributes.
<QueryFilterMapping> <String Key="searchNumber" regsearch="^0(.*)" regreplace="\1">searchNumber</String> </QueryFilterMapping>
In this example, the leading zeroes will be removed for all LDAP requests for the searchNumber filter.
You can assign additional object classes associated with the supplied contacts to the server in addition to manipulating the attribute assignments. You can also store them in the .termxml files.
<AdditionalObjectClasses> <Class>inetOrgPerson</Class> </AdditionalObjectClasses>
The .termxml files will be re-read by estos MetaDirectory at runtime for changes. After any modification, they will have to recreate the connection from the Admin to the server so that the Admin will retrieve the changed settings from the server. They can immediately assign the new terminal profile to Database Management to a database node.