On the contrary I think you suggested a solution that I never thought of.. and I thank you very much for that.. I was using the credentials the other way. I thought out credentials which represented roles like "editor", "publisher" and then started putting these in security.yml and generator.yml's. This usage obviosuly has a shortcoming of having to write to yml files in the production if we need to update/change to role of editor by adding or removing permissions (credentials). My problem is that I have contained meanings of both permission and role inside credentials.
What I need to do is to create unique credential for each permission (operation) that I need and then in order to form roles, I keep the grouping of credentials (permissions) inside my db. Then after the user with role "editor" logs in just give him the whole array of credentials associated with the role editor reading these from db Thanx once again Richtermeister wrote: > Not sure if I understand this right, but wouldn't it be better to > change the credentials the user has, instead of changing the > requirements of the application? After all, for every button you can > create a specific credential, and add this to the user on a DB level.. > > hope this helps, sorry if I misunderstand. > > Daniel > > On Apr 23, 10:04 am, Haris Zukanović <[EMAIL PROTECTED]> wrote: > >> Well, I am having a problem with credentials being inside the yml's. I >> am looking for a way to aviod this and put these inside the database. >> My problem is simply that in production environment there is a constant >> need of changing the security.yml but also generator.yml (so that >> buttons for unavailable operations are not displayed). >> This makes it difficult to maintain (merge) these yml files when doing >> new frequent updates towards production evironment.. >> Any suggestions on how to proceed with respect to how it should be done >> in symfony? >> >> >> >> Ian P. Christian wrote: >> >>> Haris Zukanović wrote: >>> >>>> Hi ppl, >>>> >>>> We use symfony 1.0 I wanted to try out the sfGuardPlugin. >>>> Does sfGuardPlugin rely on credentials that are written in yml files ? >>>> >>> rely in what sense? It allows you to use secury.yml, yes - sfGuard uses >>> the standard symfony credentials. >>> >>>> Does it work with admin generator ? >>>> >>> Yes. >>> >> -- >> Haris Zukanovic >> CEO >> Software development and research >> International Business Development, SOFTING ltd. >> >> office +387 36 318 339 >> GSM +387 61 839 069 >> >> http://www.eu-softing.com >> >> CONFIDENTIALITY NOTICE >> This e-mail and any attached files, sent by a company e - mail system, >> contains company confidential and/or privileged information and is intended >> only for the person or entity to which it is addressed and only for the >> purposes therein set forth. If you are not the intended recipient (or have >> received this e-mail in error) please notify the sender immediately and >> destroy this e-mail. Any unauthorized copying, disclosure, distribution or >> other use of, or taking of any action in reliance upon, the material in this >> e-mail by persons or entities other than the intended recipient is strictly >> forbidden. >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---