#134 slapi_search_internal_get_entry returns incorrect error code
Closed: wontfix 4 years ago by mreynolds. Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=227455

Description of problem:

If a plugin has failed to add its plugin id, instead using zero, the error code
returned is "no such object" when it should be "access denied" - it could also
be a bit more vocal in debug mode to alert the programmer that the failure is
due to plugin level authentication.

Version-Release number of selected component (if applicable):


How reproducible:

always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

batch update to FUTURE milestone

set default ticket origin to Community

Added initial screened field value.

good work for an intern

slapi_search_internal_get_entry indeed returns LDAP_NO_SUCH_OBJECT if the search returns LDAP_SUCCESS but no entries are returned.

We could log something like 'internal search (dn, base, "(|(objectclass=*)(objectclass=ldapsubentry))") with componentID == "%s" returned no entries' as SLAPI_LOG_PLUGIN level?

Note: I don't think we could correctly return ACCESS_DENIED only when the componentID is invalid.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.6 backlog

7 years ago

Metadata Update from @mreynolds:
- Custom field component reset (from Server - Plugins)
- Custom field reviewstatus reset (from Needs Review)
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)

6 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: FUTURE (was: 1.3.7 backlog)

6 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

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 issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/134

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata