-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
#494 Implements Serializable interface in the User entity #495
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,7 +18,7 @@ | |
* @author Ryan Weaver <[email protected]> | ||
* @author Javier Eguiluz <[email protected]> | ||
*/ | ||
class User implements UserInterface | ||
class User implements UserInterface, \Serializable | ||
{ | ||
/** | ||
* @var int | ||
|
@@ -163,4 +163,28 @@ public function eraseCredentials() | |
// if you had a plainPassword property, you'd nullify it here | ||
// $this->plainPassword = null; | ||
} | ||
|
||
/** @see \Serializable::serialize() */ | ||
public function serialize() | ||
{ | ||
return serialize([ | ||
$this->id, | ||
$this->username, | ||
$this->password, | ||
// see section on salt below | ||
// $this->salt, | ||
]); | ||
} | ||
|
||
/** @see \Serializable::unserialize() */ | ||
public function unserialize($serialized) | ||
{ | ||
list( | ||
$this->id, | ||
$this->username, | ||
$this->password, | ||
// see section on salt below | ||
// $this->salt | ||
) = unserialize($serialized); | ||
} | ||
} |
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.
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.
Is adding the password here a recommended practice (from the security point of view)?
Uh oh!
There was an error while loading. Please reload this page.
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.
I used the example from the documentation http://symfony.com/doc/current/security/entity_provider.html#create-your-user-entity
Uh oh!
There was an error while loading. Please reload this page.
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.
Quoted from http://symfony.com/doc/current/security/entity_provider.html#understanding-serialize-and-how-a-user-is-saved-in-the-session
Uh oh!
There was an error while loading. Please reload this page.
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.
This explanation is not very good 😕 Saying "maybe you need this ... maybe you don't" without explaining anything else doesn't look good. And then, saying "you can serialize just "id" if you want ... but maybe it doesn't work because Symfony wants more" is also confusing.
As usual, this is caused by the massive internal complexity of the security component ... so I don't know what can we do about 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.
I have to agree with you, it's quite unclear. I don't know what to do either maybe someone could enlight us on this particular topic ?