Fix 'Authorization Failed' regression when submitting eg. webform via checksum #23607
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
When a user accesses API3 (eg Activity.create, Case.create, EmailApi.send) and they are accessing via a checksum link (I tested using a drupal webform submission with a checksum) the API calls fail with "Authorization Failed". I traced this to the recently changed in #23099 API4
RecentItems::update()
I'm not certain if setting checkPermissions = FALSE is the correct thing to do here because this code is called on every post hook but I think that's effectively how it was working before.
Before
Cannot use API3 calls when "logged in" via a checksum.
After
Can use API3 calls when "logged in" via a checksum.
Technical Details
The user does not have "Access CiviCRM" but an "authenticated user" does have "Access AJAX API" and I think the checksum gives them "authenticated user" access? An alternative might be to open up permissions on RecentItems to "Access AJAX API"?
Comments
@colemanw @eileenmcnaughton per discussion in product-maintenance. This is a regression on 5.49.