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 for authentication? How do I tell symfony2 to use the user object I have in sessions to be the source of authentication so that I would not be authenticated as "anon"?
Thanks, Jaakko R On Sat, Jan 22, 2011 at 6:20 PM, taidehuone <[email protected]> wrote: > 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 proxy. I still > have no idea what causes the persistence problem - login_check appears to > work fine but the authentication is not persisted to next page load. > -- 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
