We updated two different Test systems with the CiviCRM Security Release (5.50.0, 5.49.4, 5.45.6 ESR) from 1st of June 2022. One test system has Drupal7 and CiviCRM 5.49.4, the other one has Drupal9 and CiviCRM 5.49.4. (We updated the latter to CiviCRM 5.50.1, but the problem persists.)
After the update, we cannot change Cases via Drupal Webform (which is using the CiviCRM API) anymore if we are logged in as a test user. When we try, the webform returns a success message, but the changes are not saved in CiviCRM and in the error protocoll it says:
The CiviCRM "case create" API returned the error: "Index 0 not found in api results" when called by function "postSave" on line 222 of wf_crm_webform_postprocess.inc with parameters: "Array ( [medium_id] => 1 [case_type_id] => 4 [status_id] => 1 [subject] => testsubject [custom_118] => [custom_283] => 1 [custom_6] => Array ( ) [custom_9] => [custom_120] => [custom_11] => [custom_128] => 0 [custom_12] => [custom_307] => 19940614 [custom_131] => Array ( ) [custom_15] => Array ( ) [custom_300] => [custom_139] => Array ( ) [custom_280] => [custom_18] => Array ( ) [custom_314] => Array ( ) [custom_26] => Array ( ) [custom_51] => Array ( ) [custom_121] => Array ( ) [custom_122] => Array ( ) [custom_294] => [custom_167] => 0 [custom_281] => Array ( ) [custom_295] => [custom_240] => [custom_288] => [custom_241] => [custom_290] => [custom_57] => Array ( ) [custom_249] => [custom_309] => [custom_81] => Array ( ) [custom_256] => [custom_308] => [custom_87] => Array ( ) [custom_270] => [custom_271] => [custom_272] => [custom_274] => Array ( ) [custom_92] => 0 [custom_93] => [custom_94] => [custom_95] => [custom_96] => [custom_97] => [custom_98] => [custom_277] => [client_id] => 2016 [id] => 3845 [check_permissions] => [version] => 3 ) "
We can change Cases via Drupal Webform as admins. Creating/changing Cases via the CiviCRM GUI works (as test user and admin), as well as creating/changing Cases using the CiviCRM API3 Explorer (as admin). As the latter works well, the problem cannot lie in the CiviCRM API itself, but it has to be an issue with the way Drupal webform calls the CiviCRM API. On the other hand, as the problem exists in both Drupal7 and Drupal9, and didn't occur in both of these systems before the CiviCRM Update, it cannot really be a problem in Drupal webform as well.
Did anybody meet a similar problem when updating to this Security Release, and found out why? Does anybody know if this update changed something related to permission model / user roles? Any hint is appreciated.