This behavior has been changed in the HEAD revision. Kind regards, Johannes
On Jan 28, 4:51 pm, DisTurBinG <[email protected]> wrote: > I agree, I just ran into this problem as well and noticed the same > thing. Thanks to your post! > > I don't understand why it was designed to authenticate with > __toString() isntead of getUsername() > > I believe that getUsername should be the standard for the > authentication as an obvious. To String was something I thought was > used for debugging and displaying to the front end with ease, such as > > function __toString() > { > return $this->firstName . ' ' . $this->lastName; > > } > > Anyways, something that is vague in the documentation or a mistake in > code? We will see :). Hopefully it changes! > > ~DisTurBinG > > On Jan 22, 12:31 pm, taidehuone <[email protected]> wrote: > > > I have now completely resolved this issue. > > > Your user entity - the one that implements either AccountInterface or > > AdvancedAccountInterface - must have a __toString() method which returns the > > login identifier and absolutely nothing else. This is not obvious behavior > > in my opinion. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
