Auth Block 1.0 - redirecting to the original document

Hi List, after having spent a few hours digging into the internals of the new authentication framework I am missing one feature of the old framework: In the old framework one had to define a redirect-to uri in the authentication handler. When this uri was called a request-param called

Problem with auth block

Hi, I have a sitemap which contains the following element: map:match pattern=admin/emner/* map:act type=cauth-is-logged-in map:parameter name=application value=Sublima/ map:call function=com.computas.sublima.app.controller.admin.TopicController

Re: Problem with auth block

Magnus Haraldsen Amundsen schrieb: map:match pattern=admin/emner/* map:act type=cauth-is-logged-in map:parameter name=application value=Sublima/ map:call function=com.computas.sublima.app.controller.admin.TopicController map:parameter name=mode

Re: Auth block

Hi Martin, You were right. The 1.0.0-RC2 for cocoon-pipeline-components was fine. Note that there is small error at http://cocoon.apache.org/2.2/blocks/auth/1.0/1315_1_1.html The class org.apache.cocoon.auth.StandardApplication should be replaced with

Re: Auth block

Hi Martin, Still one more correction. The org.apache.cocoon.auth.acting.* package, from cocoon-auth-impl, version 1.0.0, gives another exception: java.lang.NoSuchMethodError: org.apache.cocoon.auth.acting.LoggedInAction.getLogger()Lorg/apache/commons/logging/Log; at

Re: Auth block

Hi, just to answer my own question: the problem was due to a dependency mismatch. I had in the pom.xml the following: dependency groupIdorg.springframework/groupId artifactIdspring-jdbc/artifactId version2.5.1/version /dependency Changing the version to 2.0.6

Re: Auth block

Hi, I've still problems with the Auth blocl in 2.2. To get rid of a NoSuchClassException, it was required to add to pom.xml the following entry: dependency groupIdorg.apache.cocoon/groupId artifactIdcocoon-pipeline-components/artifactId version1.0.0/version

Re[2]: Auth block

Hi Andre, Monday, May 5, 2008, 8:52:30 PM, you wrote: AJ dependency AJgroupIdorg.apache.cocoon/groupId AJartifactIdcocoon-pipeline-components/artifactId AJversion1.0.0/version AJ /dependency I don't think that cocoon-pipeline-components 1.0.0 is already

Auth block

Hi All, I experience a problem with the Cocoon authentication block, when updating from authentication-fw. The following exception is thrown: .. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name

auth block (was Re: Action Vs Logicsheet)

a couple of times. I haven't factored that solution into anything reusable, because I haven't re-invented this wheel enough times for a general set of requirements to emerge... plus I suspect someday I will go back to using something more standard anyway. One thing nice about the auth block

Auth block: logout doesn't invalidate Sessions

Hello, after logging out I can still access the previous session by typing in the URL of the form http://foo.com/protected.xml;jsessionid=2C0C8021BCD24D4BEE48E4E4BF642EC9 All the session information is still there, I can output it on that page with something like: session:getxml

Re: Auth block: logout doesn't invalidate Sessions

Ulrich Mayring wrote: Hello, after logging out I can still access the previous session by typing in the URL of the form http://foo.com/protected.xml;jsessionid=2C0C8021BCD24D4BEE48E4E4BF642EC9 By chance I stumbled upon the encodeURL transformer and if I use that, then the session IS