[17.0] [FIX] fastapi: Running User Rule Domain#541
Merged
Conversation
Contributor
|
Hi @lmignon, |
lmignon
approved these changes
Jun 16, 2025
Contributor
|
This PR looks fantastic, let's merge it! |
Contributor
|
Congratulations, your PR was merged at ee777f1. Thanks a lot for contributing to OCA. ❤️ |
This was referenced Jun 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Currently, the res.partner rule "fastapi: Running User Rule" filters records using the user_id field (Salesperson) instead of the user_ids field (Users).
Since the authenticated_partner_id context can be empty, the rule becomes too restrictive and may deny access to the running user, which defeats the purpose it was designed for.
T-8323