Overview#

CA Directory is a LDAP Server Implementation from Computer Associates.

How it Works[1]#

CA Directory uses DSAs of different Types:

• Router DSA - A router DSA has no local data and no datastore. It can only route traffic to other DSAs.
• Data DSA - A data DSA holds data, and queries are routed to it by router DSAs. A data DSA can perform local operations, replicate updates, and route traffic to other DSAs.
• Third-party DSA - This is a DSA from an external vendor.
  

Example How a Query to an CA Directory Server Works#

DSA Router

.

• The router DSA receives a search request.
• The search specifies a branch in the Staff partition, which the router DSA knows is served by the LDAP server Staff.
• The router DSA checks the Staff server's configuration to see whether there are any special conditions for linking to that DSA. The configuration indicates that the Staff server requires that any links use LDAP.
• The router DSA uses acts as a client to make an LDAP search request of the Staff server.
• The Staff server responds with the search result (also using LDAP).
• The router DSA returns the search result to the client.

Where is the Data?#

A data DSA is always associated with a datastore, which stores the data even if the DSA is shut down. The datastore is a memory-mapped file. The DSA uses the in-memory copy of the namespace partition, and relies on the operating system memory mapping functions to keep the file copy on disk up to date.

More Information#

There might be more information for this subject on one of the following:

• CaseIgnoreString
• DXServer Commands
• DXServer Console
• DxPwdFailedAttempts
• DxPwdFailedTime
• DxPwdHistory
• DxPwdLoginTime
• LDAP Server Implementations
• Password History
• Password MUST Change

---

• [#1] - CA Directory - 12.0.15 - based on information obtained 2015-10-22