Page created: 6 Nov 2019
|
Page updated: 25 Mar 2020
The PingDirectory Server provides a means to configure a hub-like, read-only
directory server for legacy systems that require it. The
read-only directory server participates in replication but
cannot respond to any update requests from an external client. You can configure the Directory Server by setting the writability mode to internal-only, which makes the
server operate in read-only mode. Read-only mode directory servers can process update operations from
internal operations but reject any write requests from external clients. Because the Directory Server cannot accept write requests, you can configure the server to send a
referral, which redirects a client's request to a master server. The client must perform the
operation again on the server named in the referral.
Note:
For Implementers of Third Party
Extensions. Many Server SDK extensions use the
InternalConnection
interface to process operations in the server, rather than issuing LDAP requests over the
network. If an extension does so in response to an external update request, then any
Directory Server using that extension will effectively respond to external
update requests, even though the Directory Server is configured to operate in
read-only mode, as described above. One possible workaround is to split the extension into
two extensions, one for reads and one for writes, then disabling (or not deploying) the
write-only extension when configuring a Directory Server in read-only mode.