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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EZP-32333: Validate access for 'change password' menu item #92
EZP-32333: Validate access for 'change password' menu item #92
Changes from 1 commit
55f6a7d
bc879a4
7ffeb70
0363c6f
df1b5a8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we get currentUser from
$token
instead of fetching it from userService?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sadly not as
$token
is instance ofSymfony\Component\Security\Core\User\UserInterface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm.
I would say token is instance of
\Symfony\Component\Security\Core\Authentication\Token\TokenInterface
,And you can get
\eZ\Publish\Core\MVC\Symfony\Security\User
fromgetUser
, and then API user withgetAPIUser
, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, sorry, I mean
getUser
on$token
was an instance ofSymfony\Component\Security\Core\User\UserInterface
, not the token itself. I'll take a second look at this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We actually can't get user with
getAPIUser
as this method is insideeZ\Publish\Core\MVC\Symfony\Security\UserInterface
whether$token->getUser()
gives usSymfony\Component\Security\Core\User\UserInterface
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we even bother asking
TokenStorage
for the User if we store it elsewhere?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was probably used as a first resort to validate the user, but if we should actually check it via permission resolver this could be skipped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, yes if you look at interfaces, but our implementation returns
\Symfony\Component\Security\Core\User\User
we could check for it (or more precise, checking if user is instance of\eZ\Publish\Core\MVC\Symfony\Security\ReferenceUserInterface
, and act accordingly. or remove tokenStorage alltogether and just relay on userService.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0363c6f