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
For me your proposal looks more complicated, think about the following
problems:
1. No write access to the security.yml files
Depending on your setup the web process may not access those file to
update them.
2. Cleaning the cache after each update
You have to clear up the symfony cache after
On Sunday, December 12, 2010 10:27:56 PM UTC+2, Javier Garcia wrote:
Yes, you are right, I have tried it and it gives me an error about the
permissions of the file. But, what is the web process? the www-data
user? You say also depending n your setup, so is there any setup
process that allow to
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
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
