Repository navigation
[18.0][FIX] impersonate_login: read partner name with sudo on back to origin - #1047
Open
RicardCForgeFlow wants to merge 1 commit into
Open
RicardCForgeFlow wants to merge 1 commit into
RicardCForgeFlow wants to merge 1 commit into
Conversation
Contributor
|
Hi @Kev-Roche, |
JordiMForgeFlow
approved these changes
Oct 21, 2026
Author
|
Tests failing until #1045 is merged |
RicardCForgeFlow
force-pushed
the
18.0-fix-impersonate_login-back-access
branch
from
October 21, 2026 10:13
66019a0 to
a12953a
Compare
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
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.
When going back to the original user, the environment is still the impersonated user's one, which may not be allowed to read the original user (e.g. through partner record rules). Reading the partner name for the log then raises an AccessError and the session stays impersonated.