You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by "Mike M." <le...@mordent.com> on 2005/11/04 14:42:27 UTC

Protecting "live" site and cocoon offline generation problems in 1.2.x...

Hi,

I read sometime back about how you can restrict access to your "live" site by
editing the subtree_policy.xml and replacing the "world" entry with other
roles/groups.  However, when I did that, our cocoon offline generation process
no longer had access to the "live" site.  Our cocoon offline generation is
running as part of lenya (it's a workflow task / menu item we added).  Does
anyone know what user, if any, these kinds of tasks run as?  I figured it would
run as the person performing the action, but unfortunately that doesn't appear
to be the case.  If it's not running as any user, how can we force it to do so,
or give it access somehow?

Thanks!
-mm



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Protecting "live" site and cocoon offline generation problems in 1.2.x...

Posted by Michael Wechner <mi...@wyona.com>.
Mike M. wrote:

>Hi,
>
>I read sometime back about how you can restrict access to your "live" site by
>editing the subtree_policy.xml and replacing the "world" entry with other
>roles/groups.  However, when I did that, our cocoon offline generation process
>no longer had access to the "live" site.  Our cocoon offline generation is
>running as part of lenya (it's a workflow task / menu item we added).  Does
>anyone know what user, if any, these kinds of tasks run as? 
>

as localhost. You might want to add your localhost (127.0.0.1 resp. the 
appropriate IP address) to the policy and open it for localhost.

HTH

Michi

> I figured it would
>run as the person performing the action, but unfortunately that doesn't appear
>to be the case.  If it's not running as any user, how can we force it to do so,
>or give it access somehow?
>
>Thanks!
>-mm
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>For additional commands, e-mail: user-help@lenya.apache.org
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org