#50429 Ticket 50428 - Log the actual base DN when the search fails with "invalid attribute request"
Closed by spichugi. Opened by tbordaz.
tbordaz/389-ds-base ticket-50428  into  master

Download 50429.patch

Bug Description:
When a search request contains invalid parameters (attribute list with empty attribute
name, unknown scope, invalid filter..) the search is rejected but the access log
contains a wrong base search: ... SRCH base="(null)"...
This is because it does not use for logging the variable that gather the actual base ('rawbase')

Fix Description:
Use 'rawbase' value for logging

https://pagure.io/389-ds-base/issue/50428

Reviewed by: ?

Platforms tested: F28

Flag Day: no

Doc impact: no

rebased onto 278f5aac6d85221b5c27064f7dfb9b8bf6b4088a

Pull-Request has been merged by tbordaz

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3487

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Metadata