cziegeler    2002/07/05 00:22:31

  Modified:    src/documentation/xdocs/developing/webapps
                        authentication.xml
  Log:
  Updated docs
  
  Revision  Changes    Path
  1.4       +6 -4      
xml-cocoon2/src/documentation/xdocs/developing/webapps/authentication.xml
  
  Index: authentication.xml
  ===================================================================
  RCS file: 
/home/cvs/xml-cocoon2/src/documentation/xdocs/developing/webapps/authentication.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- authentication.xml        25 Jun 2002 08:52:58 -0000      1.3
  +++ authentication.xml        5 Jul 2002 07:22:30 -0000       1.4
  @@ -134,20 +134,22 @@
           <p>The <em>auth-login</em> action uses the handler parameter to call the
             authentication resource of this handler. This authentication resource 
needs to
             know the information provided by the user. For each piece of information 
an own
  -          parameter is created which name starting with "parameter_". So in the 
example
  +          parameter is created which name starts with "parameter_". So in the 
example
             above, the authentication resource gets two parameters: userid and 
password. As
             the values for these parameters were send by a form they need to be 
passed on
             to the authentication resource. If you use "{request:...}" for the value 
of a
             parameter, the <em>auth-login</em> action will pass the actual value of 
that request
             parameter to the authentication resource (by using the input modules 
concept
             of Cocoon).</p>
  -        <p>If the user is not authenticated with this handler, the framework calls
  +        <p>If the user is not already authenticated with this handler, the 
framework calls
             the authentication resource and passes it the parameters. If this
  -          authentication is successful, the action returns an empty map and the 
sitemap
  +          authentication is successful, the action returns a map and the sitemap
             commands inside the map:act are executed. If the authentication fails, 
these
             are skipped.</p>
           <p>If the authentication is successful, a session object is created on
  -          the server (if not already done). </p>
  +          the server (if not already done). If the authentication fails, the error
  +          information delivered by the authentication resource is stored into the
  +          <em>temporary</em> context (which is named simply 'temp').</p>
        </s2>
        <s2 title="The authentication resource">
           <p>The last chapters described the authentication process but left out
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to