I've put this off because we're not yet using Security component. In response to what Ben mentioned, the FB login process is very view-centric (and worse, OAuth-centric), so relying on the Javascript SDK is a quick win.
There's no reason you can't rely on JS to handle the login/registration flow, and still create a provider. The Security component provider would just have to check for \Facebook::getUser(), which will return a FB UID if someone is connected. You can then resolve that FB UID to a database user. Presenting the Javascript SDK as a login option would be up to the developer, but it's outside the scope of the firewall in my opinion. I would suggest that if anyone implements the above, they consider contributing to: https://github.com/kriswallsmith/FacebookBundle It'd be more helpful to the community to build up an existing Facebook bundle (which already has some essentials for connecting the API) than end up with several competing ones. On Wed, Dec 1, 2010 at 6:13 AM, Benjamin Eberlei <[email protected]>wrote: > i tried this with symfony 1 and i hated it. Facebook authentication is > very view centric, so i switched to using the javascript sdk. > > On Wed, 1 Dec 2010 10:34:20 +0100, noel guilbert <[email protected]> > wrote: > > Hi, > > > > I'm working on something similar actually (login in a facebook > > application). > > I hope I will have something for the end of the week. > > > > Noel > > > > > > On Wed, Dec 1, 2010 at 6:47 AM, Lukas Kahwe Smith > > <[email protected]>wrote: > > > >> Hi, > >> > >> just wondering if someone has worked on implementing a facebook connect > >> provider for the Symfony2 security firewall? ideally it would allow me > to > >> authenticate to facebook but allow to easily hook in to read out data > >> from > >> my local database to setup the user object. actually i might also want > to > >> automatically sync some graph data from facebook into my local > database. > >> also seems like a good use case to illustrate how a token based > >> authentication works. > >> > >> regards, > >> Lukas Kahwe Smith > >> [email protected] > >> > >> > >> > >> -- > >> 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 [email protected] > >> To unsubscribe from this group, send email to > >> > [email protected]<symfony-devs%[email protected]> > <symfony-devs%[email protected]<symfony-devs%[email protected]> > > > >> For more options, visit this group at > >> http://groups.google.com/group/symfony-devs?hl=en > >> > > > > > > > > -- > > Noël GUILBERT > > http://www.noelguilbert.com/ > > Twitter : http://twitter.com/noelguilbert > > http://www.sensiolabs.com > > http://www.symfony-project.com > > Sensio Labs > > Tél: +33 1 40 99 80 80 > > -- > 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- jeremy mikola -- 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 [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-devs?hl=en
