You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jean-Christophe Kermagoret <jc...@openbluelab.org> on 2007/01/11 17:38:16 UTC
Cocoon 2.2, portal and cauth problem
Hi,
I don't want DB auth, so I comment in
cocoon-portal-sample/src/main/resources/COB-INF/config/avalon/auth-cauth.conf
the part about DBSecurityHandler and uncomment the one with
PipelineSecurityHandler.
But even if I change the file (and remove the target directory in
cocoon-portal-sample and cocoon-webapp with 'mvn -o clean' in each
directory), I finally have the original file with DBSecurityHandler in
my cocoon-webapp when I try 'mvn -o install jetty:run' in my webapp
directory !!!
What's wrong ?
Thanks for the help
--
Jean-Christophe Kermagoret
jck@OpenBlueLab.Org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: How to pass {ID} into protected, mounted sitemap?
Posted by Carsten Ziegeler <cz...@apache.org>.
Stan Dyck wrote:
> I've got an authenticating pipeline something like this:
>
> <map:match pattern="*">
> <map:act type="auth-protect">
> <map:parameter name="handler" value="myhandler"/>
>
> <map:match pattern="protected">
> <map:generate src="resource1.xml"/>
> <map:transform src="resource2html.xsl">
> <map:parameter name="uid" value="{ID}"/>
> </map:transform>
> <map:serialize/>
> </map:match>
>
> <map:match pattern="subdir/**">
> <map:mount uri-prefix="subdir" check-reload="yes"
> src="subdir/sitemap.xmap"/>
> </map:match>
>
> </map:act>
> </map:match>
>
> The idea is to protect a resource in a root directory and all the
> resources in a mounted subdirectory. This works fine except for one
> thing. If the sitemap in the subdir directory has something like this:
>
> <map:match pattern="subprotect">
> <map:generate src="subresource.xml"/>
> <map:transform src="subresource2html.xsl">
> <map:parameter name="uid" value="{ID}"/>
> </map:transform>
> <map:serialize/>
> </map:match>
>
> I can't get the uid parameter to inject the login id into the
> subresource2html.xsl stylesheet. Can someone help me out with this? What
> do I need to do to pass the user id into a protected, mounted sitemap?
>
The {ID} is only available within the "auth-protect" action in the
sitemap. The easiest way for you is to just repeat the action inside
your subsitemap to make the {ID} available:
> <map:match pattern="subprotect">
> <map:act type="auth-protect">
> <map:parameter name="handler" value="myhandler"/>
> <map:generate src="subresource.xml"/>
> <map:transform src="subresource2html.xsl">
> <map:parameter name="uid" value="{ID}"/>
> </map:transform>
> <map:serialize/>
> </map:act>
> </map:match>
HTH
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
How to pass {ID} into protected, mounted sitemap?
Posted by Stan Dyck <sg...@standyck.com>.
I've got an authenticating pipeline something like this:
<map:match pattern="*">
<map:act type="auth-protect">
<map:parameter name="handler" value="myhandler"/>
<map:match pattern="protected">
<map:generate src="resource1.xml"/>
<map:transform src="resource2html.xsl">
<map:parameter name="uid" value="{ID}"/>
</map:transform>
<map:serialize/>
</map:match>
<map:match pattern="subdir/**">
<map:mount uri-prefix="subdir" check-reload="yes"
src="subdir/sitemap.xmap"/>
</map:match>
</map:act>
</map:match>
The idea is to protect a resource in a root directory and all the
resources in a mounted subdirectory. This works fine except for one
thing. If the sitemap in the subdir directory has something like this:
<map:match pattern="subprotect">
<map:generate src="subresource.xml"/>
<map:transform src="subresource2html.xsl">
<map:parameter name="uid" value="{ID}"/>
</map:transform>
<map:serialize/>
</map:match>
I can't get the uid parameter to inject the login id into the
subresource2html.xsl stylesheet. Can someone help me out with this? What
do I need to do to pass the user id into a protected, mounted sitemap?
StanD.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.2, portal and cauth problem
Posted by Carsten Ziegeler <cz...@apache.org>.
The portal in trunk is now working for me again (well, parts of it are
working).
I disabled the database authentication (reverting to the pipeline based
auth), disabled the automatic cforms transformation (the recent changes
to cforms seem to cause problems) and disabled the ajax support.
HTH
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.2, portal and cauth problem
Posted by Jean-Christophe Kermagoret <jc...@openbluelab.org>.
Ok, I tried but indeed there are a few problems...
I let you dive into your beast ;-)
I'm waiting impatiently for this release...
Thanks for your great job
Carsten Ziegeler wrote:
> Jean-Christophe KERMAGORET wrote:
>
>>Are you using another portal, like jetspeed ?
>
> No :)
>
>
>>I'm using intensively Cocoon Portal, and I'll be happy to help you to
>>make Cocoon portal workgin again with 2.2
>
> Great!
>
>>I'm available tomorrow to make this job, maybe I'll ask you for help
>>
>
> I'm not sure when I will have time for this, perhaps on saturday or
> early next week. I'll keep you posted.
>
> Carsten
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
--
Jean-Christophe Kermagoret
jck@OpenBlueLab.Org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.2, portal and cauth problem
Posted by Carsten Ziegeler <cz...@apache.org>.
Jean-Christophe KERMAGORET wrote:
> Are you using another portal, like jetspeed ?
No :)
> I'm using intensively Cocoon Portal, and I'll be happy to help you to
> make Cocoon portal workgin again with 2.2
Great!
>
> I'm available tomorrow to make this job, maybe I'll ask you for help
>
I'm not sure when I will have time for this, perhaps on saturday or
early next week. I'll keep you posted.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.2, portal and cauth problem
Posted by Jean-Christophe KERMAGORET <jc...@openbluelab.org>.
Are you using another portal, like jetspeed ?
I'm using intensively Cocoon Portal, and I'll be happy to help you to
make Cocoon portal workgin again with 2.2
I'm available tomorrow to make this job, maybe I'll ask you for help
Bye
Carsten Ziegeler a écrit :
> I haven't tested the portal block for a long time. In the meantime we
> changed several things in the core regarding configuration. So it could
> be that the current portal sample needs some updates before it works again.
>
> I'm currently working on the hsqldb block and hope to get it finished
> tonight. Next would be the OJB block, followed by the portal block. So I
> hope everything will work again very soon.
>
> Carsten
>
> Jean-Christophe Kermagoret wrote:
>
>> Hi,
>> I don't want DB auth, so I comment in
>> cocoon-portal-sample/src/main/resources/COB-INF/config/avalon/auth-cauth.conf
>> the part about DBSecurityHandler and uncomment the one with
>> PipelineSecurityHandler.
>>
>> But even if I change the file (and remove the target directory in
>> cocoon-portal-sample and cocoon-webapp with 'mvn -o clean' in each
>> directory), I finally have the original file with DBSecurityHandler in
>> my cocoon-webapp when I try 'mvn -o install jetty:run' in my webapp
>> directory !!!
>>
>> What's wrong ?
>>
>> Thanks for the help
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.2, portal and cauth problem
Posted by Carsten Ziegeler <cz...@apache.org>.
I haven't tested the portal block for a long time. In the meantime we
changed several things in the core regarding configuration. So it could
be that the current portal sample needs some updates before it works again.
I'm currently working on the hsqldb block and hope to get it finished
tonight. Next would be the OJB block, followed by the portal block. So I
hope everything will work again very soon.
Carsten
Jean-Christophe Kermagoret wrote:
> Hi,
> I don't want DB auth, so I comment in
> cocoon-portal-sample/src/main/resources/COB-INF/config/avalon/auth-cauth.conf
> the part about DBSecurityHandler and uncomment the one with
> PipelineSecurityHandler.
>
> But even if I change the file (and remove the target directory in
> cocoon-portal-sample and cocoon-webapp with 'mvn -o clean' in each
> directory), I finally have the original file with DBSecurityHandler in
> my cocoon-webapp when I try 'mvn -o install jetty:run' in my webapp
> directory !!!
>
> What's wrong ?
>
> Thanks for the help
>
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.2, portal and cauth problem
Posted by Carsten Ziegeler <cz...@apache.org>.
Jean-Christophe Kermagoret wrote:
> Hi,
> I don't want DB auth, so I comment in
> cocoon-portal-sample/src/main/resources/COB-INF/config/avalon/auth-cauth.conf
> the part about DBSecurityHandler and uncomment the one with
> PipelineSecurityHandler.
>
> But even if I change the file (and remove the target directory in
> cocoon-portal-sample and cocoon-webapp with 'mvn -o clean' in each
> directory), I finally have the original file with DBSecurityHandler in
> my cocoon-webapp when I try 'mvn -o install jetty:run' in my webapp
> directory !!!
>
> What's wrong ?
>
Dump question just to be sure: you did a mvn -o install in the
cocoon-portal-sample directory before the mvn -o install in the
cocoon-webapp directory?
Usually when I test changes I clean the block I want to test, do then an
install there and then do a clean/install/jetty run in the webapp directory.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org