I've worked on a similar project. As the system required authentication for every possible action, I've created every module in the frontend. Then there was a login module which, after positive authentication, set a variable in the $this->getUser() property indicating rights the user had.
Then in every action I've executed a method which returns true if for positive authorization. and in case of unauthorized access, user was redirected to login site. Project was small, so I could hardcode every possible authentication level. The authentication and authorization was performed in a class with static methods, this class was in the /lib so it was autoloaded. Such way is quite comfortable for small projects which do not need to perform complicated ACL controls or provide dynamic access level. Regards, Maciej Aleksandrowicz. 2010/10/20 Martin Ibarra Cervantes <ibarra.cervan...@gmail.com>: > you can try with credentials > > http://vit.free.fr/symfony/0.6.3/security.html > > and a frontend public, a frontend private , and a backend private for > your admin add and remove on the tables. > the frontend private you can use credentials and your file security on > your config module. > > > > On Wed, Oct 20, 2010 at 4:52 AM, Jaume <jaum...@gmail.com> wrote: >> Hello. I am learning symfony to make a web application on a virtual >> school. >> >> My problem is I need different types of Admin, each of which can do >> different things. For example, the teacher can only view reports for >> students, the Director may set the courses and subjects and the >> administrator can add and sign remove students. >> >> In addition, students will need to authenticate before each session. >> >> So, I need a frontend to the pupils, but not how to do the 3 different >> backends for the 3 types of admins. >> >> Anyone can help me? >> >> Thank you very much! >> >> -- >> 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 >> > > -- > 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 > -- 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
