Hi Christian, The API already exists as is internally managed. It's fully RESTful. It maintains access for users to a variety of apps et al.
Therefore I can't use OAuth, but maybe I can look at those plugins to see how they have implemented it. Cheers, Chris On Aug 17, 8:34 am, Christian Schaefer <cae...@gmail.com> wrote: > hi chris, > > I would suggest to not reinvent the wheel and look for a solution that > uses sfguard on the inside and oauth to the outside. > I haven't tested them myself yet but there are some plugins in that > area already. > > cheers > /christian > > On Aug 16, 5:31 pm, catchamonkey <ch...@sedlmayr.co.uk> wrote: > > > > > Hi all, > > > What are your thoughts on implementing an existing ACL which is > > accessed through an API into symfony 1.4? > > I would ideally like to use sfGuard and replace the main elements of > > signin, signout and any permission calls et al. > > > Do you think it would be best to start from scratch or build on top of > > sfGuard(Doctrine) > > > Regards, > > Chris (catchamonkey) -- 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 symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
