LX0-104 · Question #146
Which of the following is the most appropriate method of debugging problems concerning ACLs?
The correct answer is A. Stop the OpenLDAP server daemon and run the command slapd -d 128. To debug ACL problems in OpenLDAP, the slapd daemon should be run in debug mode with a specific level that enables ACL logging.
Question
Options
- AStop the OpenLDAP server daemon and run the command slapd -d 128.
- BStop the OpenLDAP server daemon and run the command slapd -d 32.
- CStop the OpenLDAP server daemon and run the command slapd -log_acl.
- DStop the OpenLDAP server daemon and run the command slapd -debug_acl.
How the community answered
(23 responses)- A78% (18)
- B4% (1)
- C4% (1)
- D13% (3)
Why each option
To debug ACL problems in OpenLDAP, the `slapd` daemon should be run in debug mode with a specific level that enables ACL logging.
A high debug level like 128 (0x80) in `slapd -d 128` explicitly enables logging related to Access Control List (ACL) processing, allowing administrators to see how ACLs are evaluated and identify issues with permissions. This provides detailed output on ACL matching and failures.
A debug level of 32 (0x20) is typically for basic connection and operation logging, which is insufficient for detailed ACL debugging.
The `slapd` command does not have a `-log_acl` option for direct ACL logging; logging levels are controlled via the `-d` option.
The `slapd` command does not have a `-debug_acl` option for direct ACL debugging; logging levels are controlled via the `-d` option.
Concept tested: OpenLDAP ACL debugging
Source: https://www.openldap.org/doc/admin24/debugging.html
Topics
Community Discussion
No community discussion yet for this question.