Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Security] InMemoryUserProvider now concerns whether user's password is changed when refreshing#13627

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:2.3fromissei-m:in-memory-user-provider
Oct 5, 2015

Conversation

@issei-m
Copy link
Contributor

QA
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets-
LicenseMIT
Doc PR-

When a user has changed own password, I want to logout any sessions which is authenticated by its user except changer itself.

DaoAuthenticationManager::checkAuthentication() method seems to concern about it.

But, this situation actually never happens because both users that will be passed to this method are always identical in re-authentication.
It's because the token refreshes own user viaContextListener before re-authentication.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

What about keeping the original$user variable and keep the next line identical to what it was before.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Like this?

publicfunctionloadUserByUsername($username){$user =$this->getUser($username);returnnewUser($user->getUsername(),$user->getPassword(),$user->getRoles(),$user->isEnabled(),$user->isAccountNonExpired(),$user->isCredentialsNonExpired(),$user->isAccountNonLocked());}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@issei-m I think so

@issei-missei-mforce-pushed thein-memory-user-provider branch fromdebb422 to729902aCompareAugust 10, 2015 13:08
@issei-m
Copy link
ContributorAuthor

@fabpot@aitboudad Thanks for your reviewing! Now I updated PR and rebased onto 2.3 branch.

@fabpot
Copy link
Member

Thank you@issei-m.

@fabpotfabpot merged commit729902a intosymfony:2.3Oct 5, 2015
fabpot added a commit that referenced this pull requestOct 5, 2015
…s password is changed when refreshing (issei-m)This PR was merged into the 2.3 branch.Discussion----------[Security] InMemoryUserProvider now concerns whether user's password is changed when refreshing| Q             | A| ------------- | ---| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -When a user has changed own password, I want to logout any sessions which is authenticated by its user except changer itself.[DaoAuthenticationManager::checkAuthentication()](https://github.com/symfony/symfony/blob/2.3/src/Symfony/Component/Security/Core/Authentication/Provider/DaoAuthenticationProvider.php#L59) method seems to concern about it.But, this situation actually never happens because both users that will be passed to this method are always identical in re-authentication.It's because the token refreshes own user via [ContextListener](https://github.com/symfony/symfony/blob/2.3/src/Symfony/Component/Security/Http/Firewall/ContextListener.php#L90) before re-authentication.Commits-------729902a [Security] InMemoryUserProvider now concerns whether user's password is changed when refreshing
@issei-missei-m deleted the in-memory-user-provider branchOctober 5, 2015 15:23
This was referencedOct 27, 2015
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@issei-m@fabpot@aitboudad

[8]ページ先頭

©2009-2025 Movatter.jp