Note: this is an abstract component, that cannot be instantiated.
Access Control Handlers manage the application-wide access control. The Oracle Unified Directory access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
Note that Oracle Unified Directory also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the BYPASS_ACL privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
The following Access Control Handlers are available in the server :
These Access Control Handlers inherit from the properties described below.
A description of each property follows.
|Basic Properties:||Advanced Properties:|
|Description||Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem. |
|Admin Action Required||None|
|Description||Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation. |
|Allowed Values||A java class that implements or extends the class(es) :|
|Admin Action Required||The Access Control Handler must be disabled and re-enabled for changes to this setting to take effect|