Hi,

thank you for all comments so far. First let me say, that I
was not able to configure different/"overwrite" login modules
at all. No *.yml I used did that. Might be I missed something.
I also did not try to 'hack' it into the configuration while
runtime. And whether this should be possible or not in Symfony
is to be discussed in another list I think.

Thank you XAN for your explanations, but you would not have to do
that for me... ;-) So to get you at this point, my applications are
made of plug-ins where the apps' modules are only for customization
for different customers. So for me, applications are just
"composed instances" and plug-ins make the application stuff.
But that's not the point. Plug-ins handle so much different things
that do also include different "semantic user contexts". So for
different user types/roles in a "composed application" I need to
set-up different Symfony contexts. And I want to do that by "separating
concerns" in separate modules of my several plug-ins. I do not want to
stick on the one globally configured login method (which is in a plug-in
module though), you see? That's it, not more.

So I now do that by "catching my semantic contexts" in the globally (app  
level)
configured login action and redirect to my special ones having their own  
templates
too. That is not such a problem, but it could be easier: by  
configuration...

Thanks you!
Jan




On Thu, 12 Nov 2009 05:15:47 +0100, XAH <hanov.rus...@gmail.com> wrote:

>
> My english is not good enough but i'll try to tell about some usefull
> concepts in symfony (i'm symfony developer for the last almost 3
> years).
>
> Module in application is the thing that do some determinate work in
> application (set of actions). For example, security module - do login
> and logout stuff. Application - set of modules that provide
> determinate context. IMHO in one context cannot be more than one
> different ways to decide how to authorize users. So, the question that
> must worry you is not "how to use different login modules" but "why do
> you want to use different login modules"
>
> On 12 ноя, 00:30, jp <jph...@googlemail.com> wrote:
>> Hi,
>>
>> security actions are defined in apps/myapp/settings.yml
>> Is it possible to overwrite those settings for a module
>> so I can have different login modules etc. ?
>> I tried settings.yml and app.yml in mymodule/config
>> containing
>>
>> all:
>>    .actions:
>>      login_module:           xyz
>>      login_action:           xyz
>>      secure_module:          xyz
>>      secure_action:          xyz
>>
>> With no success. Do you have any ideas?
>>
>> Thank you!
>> Jan
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to