Hey Javi, first, the credentials are in the security.yml, not view.yml, and secondly, the proper approach is to manage what credentials a user has rather than managing what credentials an action/module requires. So, the current approach of coding credentials into the system files and assigning/managing them via admin modules is the best practice and should not be limiting your boss in any way.
Daniel On Nov 25, 11:02 am, Javier Garcia <tirengar...@gmail.com> wrote: > Hi, > > as you know you can edit the credentials of an action or a module > going to file view.yml of the module and editing them. > > Our boss doesn't want to go to the files to edit the credentials in > each view.yml file, but wants to have a form where he can select the > modules and the actions of the application and give them the > credentials. > > What would be your approach? > > Regards > > Javi -- 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
