cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sonny Sukumar" <>
Subject 3 simple auth questions...
Date Sun, 17 Aug 2003 00:31:11 GMT

These 2 questions are based on this doc:

1.) The doc states "If the authentication is successful, a session object is 
created on the server (if not already done).  If the authentication fails, 
the error information delivered by the authentication resource is stored 
into the temporary context (which is named simply 'temp')."

Question: Where is this 'temp' context stored, if not in the session?

2.) For the auth-login action, request parameters are passed to it like:

    <map:parameter name="parameter_userid" value="{request:name}"/>
    <map:parameter name="parameter_password" value="{request:password}"/>

Question: Is this "request:" syntax generally available to pass request 
params to all actions?

3.) A handler is also configured like this:

   <handler name="unique">
      <!-- The login resource -->
      <redirect-to uri="cocoon:raw://loginpage"/>
      <authentication uri="cocoon:raw://authenticationresource"/>

Question: Is it necessary to use the "raw:" subprotocol here for not 
forwarding request params?

It says "...this resource is requested by the framework with the given 
parameters from the auth-login action" referring to the authentication 
resource, so perhaps the "raw:" subprotocol is there to prevent duplicate 
request params?  I'm just guessing here...



The new MSN 8: advanced junk mail protection and 2 months FREE*

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message