#48197 error texts from preop plugins not sent to client
Closed: wontfix None Opened 6 years ago by lkrispen.

If a preop plugin aborts an operation in an ldbm backend and sets an error text to the pblock this is not sent to the client, only the error code.

It works correctlyfor the dse database


Is there a reproducble test case? I did some testing with uid uniqueness plugin, and in that case the preop functionm sends the result, so even if you set the result text in the pblock it is ignored(becuase the result was already sent).

If I don't send the result from the preop function, then my client does receive my error text:

{{{
preop_modify(....)
...
...
errtext2 = slapi_ch_strdup("mark's error text");
slapi_pblock_set(pb, SLAPI_PB_RESULT_TEXT, errtext2);
slapi_pblock_set(pb, SLAPI_RESULT_CODE, &result);
//slapi_send_ldap_result(pb, result, 0, errtext1, 0, 0);
}}}

the uiduniqeness is BE_TXN_PREOP plugin, and if one of these fail the result message is set:

slapi_pblock_get(pb, SLAPI_PB_RESULT_TEXT, &ldap_result_message);

This is missing for SLAPI_PLUGIN_BE_PRE_MODIFY_FN

Thanks for clarifying the issue Ludwig.

bff826b..70fa356 master -> master
commit 70fa356
Author: Mark Reynolds mreynolds@redhat.com
Date: Fri Jun 12 10:18:34 2015 -0400

Metadata Update from @lkrispen:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.4.0

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/1528

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

a year ago

Login to comment on this ticket.

Metadata