Thannks very much!!!
the problem was the declaration of the parameter in  the do-login match.

best regards
manuel ottaviano


[EMAIL PROTECTED] escribió:
Hi Manuel,
that page helped me a  lot with my authentication issues:
http://cocoon.apache.org/2.1/developing/webapps/authentication/authenticating_user.html <http://cocoon.apache.org/2.1/developing/webapps/authentication/authenticating_user.html> There, it is also stated, that your parameters have to start with 'parameter_'; e.g. my part of this looks like that:

<map:match pattern="do-login">
        <!-- try to login -->
        <map:act type="auth-login">
          <map:parameter name="handler" value="indexhandler"/>
<map:parameter name="parameter_name" value="{request-param:username}"/> <map:parameter name="parameter_pw" value="{request-param:password}"/>
          <map:redirect-to uri="protected-first"/>
        </map:act>
        <!-- something was wrong, try it again -->
        <map:redirect-to uri="login"/>
      </map:match>

in my authenticate.xsl, I get these parameters as follows:
<xsl:param name="name"/>
<xsl:param name="pw"/>

authenticate is in an extra pipeline in my sitemap:
<map:pipeline internal-only="true">
      <!-- Authentifizierung -->
      <map:match pattern="authenticate">
        <map:generate src="documents/xml/userlist.xml"/>
        <map:transform src="documents/stylesheets/authenticate.xsl">
          <map:parameter name="use-request-parameters" value="true"/>
        </map:transform>
        <map:serialize type="xml"/>
      </map:match>

regards
Marco




2006/7/27, Manuel Ottaviano < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    I've tested the application inside the authentication process.
    I remove the internal only attribute and I change the action of
    the form
    (from do-login to authenticate)
    I see the correct XML. :(
    But authentication still no works .
    I've also add to the do-login pipeline process the POST parameters
    that
    cocoon receives from the form..


    <map:match pattern="do-login">
            <!-- try to login -->
            <map:act type="auth-login">
              <map:parameter name="handler" value="demohandler"/>
    <map:parameter name="parameter_name" value="{request-param:user}"/>
    <map:parameter name="password" value="{request-param:password}"/>
    <map:parameter name="product" value="{request-param:product}"/>
              <map:redirect-to uri="product"/>
            </map:act>
            <!-- something was wrong, try it again -->
            <map:redirect-to uri="login"/>
          </map:match>

    What's going on?
    best regards
    manuel

    On 7/27/06, Manuel Ottaviano <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:
    >
    >> ...but if I create a static XML file as output of the same
    >> application and
    >> I put in the auth URI the authentification framework works...
    >
    > Did you check that your other pipeline generates the exact same
    output?
    > Including no identical namespaces (or none if not required)?
    >
    > You can try this by removing the internal-only description.
    >
    > You could also use the LogTransformer to verify what's produced by
    > your MySQL pipeline when you connect it.
    >
    > HTH,
    > -Bertrand
    >
    >
    ---------------------------------------------------------------------
    > To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    > For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    >
    >
    >


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to