I think you're right to have created 3 bundles to manage the big parts of your site. However, I think you should create a 4th bundle to offers some services (see the doc for the service concept) for your business classes that will manipulate all your entities (and maybe other technical services like the mail service). This service bundle will NOT have any controller and will NOT be routed in routing.yml because the only aim of this bundle is to be a service container.
Hope that help you. On 24 juil, 09:51, Bouki <jonathan.boko...@gmail.com> wrote: > Hi > > I have trouble doing what I want by following the symfony book about > security. > > My website is divided into 3 parts, each one is designed for a > different user : > - everyone (not authentified) : the standart website > - members : a reserved area (the url for all the members things are / > members/.*) > - admin : the admin zone (url /admin/.*) > > Both members and admin have their areas that are not at all the same. > > First I think I didn't understand the bundle concept, because the > first time I tried to split my project into 3 bundles, one for each > area. > However this would have caused issues with entities because all these > 3 bundles shares the same entities, so where should I put these > entities ?! > So I finally put all in one bundle but it doesn't feel right too... > > So what should I put in my security.yml to have 2 login/logout pages, > and 2 different restricted area ? I believe multiple firewalls is the > solution however I didn't find any documentation about this. -- 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
