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 t
It is worth mentioning that the user object IS stored into sessions by
symfony2 itself and the session IS persisted over page loads, but the
session data is not used to authenticate the user after login_check, and I
am authenticated as "anon" again. What part of symfony2 determines what data
to use
Hi,
That sounds logical, all the login configuration is now listed under the
main firewall and there are no other firewalls. I also created an access map
rule for anonymous users for the login page as both you and the master docs
suggest. It did not solve or change the situation and the weird php
I have successfully fixed the PHP notice error, but the persistence problem
still exists.
I had a private id field in one of the associated entities. PHP's sleep
functionality does not work on private properties and this resulted in a
notice even though the associated entity was replaced with a pr
On Fri, 21 Jan 2011 00:21:28 +0200, taidehuone
wrote:
> Hi,
>
> I've been working on a Doctrine2 based authentication system for a
while. I
> have successfully created the security controller, related views and
> configured config.yml as described in master docs. I can get to a login
> form
> fin
Hi,
I've been working on a Doctrine2 based authentication system for a while. I
have successfully created the security controller, related views and
configured config.yml as described in master docs. I can get to a login form
fine and when I click "submit", the login data is processed on the serve
