LFCS · 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 Access Control List (ACL) issues in OpenLDAP, the server should be restarted with the debug level 128 to specifically enable logging for ACL processing.
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
(35 responses)- A94% (33)
- B3% (1)
- C3% (1)
Why each option
To debug Access Control List (ACL) issues in OpenLDAP, the server should be restarted with the debug level 128 to specifically enable logging for ACL processing.
Running `slapd` with the `-d 128` option enables verbose debugging output specifically for Access Control List (ACL) processing, providing detailed information on how ACLs are being evaluated and applied, which is critical for troubleshooting access issues.
The `-d 32` option typically enables logging for configuration file processing and schema checking, not specifically for ACL debugging.
There is no standard `slapd` command-line option called `-log_acl` for debugging ACLs; debugging levels are specified numerically with `-d`.
There is no standard `slapd` command-line option called `-debug_acl` for debugging ACLs; debugging levels are specified numerically with `-d`.
Concept tested: OpenLDAP ACL debugging
Source: https://www.openldap.org/doc/admin24/appendix-a.html
Topics
Community Discussion
No community discussion yet for this question.