Hail community, I ran into a bit of a snag using a custom authentication provider and wanted to know if anyone knows anything about this.
I am tasked with allowing users to login via their gmail account and upon successful authentication by gmail their token will be valid for them to use certain user level features of the app. The app uses a conventional doctrine user entity class as the user provider and users can have intrinsic accounts with this user provider but for those who authenticate by gmail their user identity is not to be persisted, rather they can use that token on a per authentication basis never becoming a persisted user entity. The problem that I've had is that the gmail authentication happens fine and I can tell the authentication sequence happens because I've followed it with print break statements every step of the way to ensure that its successful. The problem lies in after the authentication sequence has happened, I keep getting a message from the DaoAuthenticationProvider class saying: 'The presented password is invalid.' My problem is that I do not understand why the DaoAuthenticationProvider is doing a checkAuthentication if I've done setAuthenticated(true) in the token after successful gmail authentication. Can anyone help me with this? Thanks -- 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 developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
