The PingDirectory server provides a powerful criteria subsystem that allows it to match connections, requests, responses, entries, and references based on a wide variety of characteristics.
Criteria can be used in many ways in the server. Some of these include:
- When determining which client connection policy should be assigned to a connection
- When determining which log messages should be recorded in an access log
- When determining which types of requests should be allowed over an
insecure connection if the
reject-insecure-requestsglobal configuration property is set to true - When determining which types of requests should be allowed over an
unauthenticated connection if the
reject-unauthenticated-requestsglobal configuration property is set to true - When determining which types of bind requests should be forwarded to another server when pass-through authentication is enabled
- When determining which operations should automatically use assured replication.
- When determining which entries should be automatically updated to use entryUUID as the naming attribute
- When determining which types of delete operations should be processed as soft deletes.
- When determining which types of add and modify operations should result in “account created” and “account updated” account status notifications
- When determining the types of operations for which a custom plugin should be invoked