Hi again, thanks for your responses. What about just reading/writing each file security.yml looking for the "credentials:" key ? Then I would parse each file looking for the line where the "credentials:" key is and would add/remove credentials in that line...
On Nov 26, 8:24 pm, pghoratiu <[email protected]> wrote: > You should do the following: > - design tables to store info about: modules/actions/user/permission > - develop another security filter (that would replace the current > security filter) > that would use the new source for the credential data. > > gabriel > > On Nov 25, 9:02 pm, Javier Garcia <[email protected]> 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. > > > Ourbossdoesn'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 [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-users?hl=en
