Thanks, Carsten.
Is there an example of accessing the user data somewhere? Is the
information about the user obtained from the handler resource?
Some other things I am unclear on:
The doc says the authentication resource can be a Java class. How is that
done?
The last sentence in section 3.3 says "This data node is then added inside
the "login" tag of the login resource (see previous chapter)." Assuming you
really mean section 3.2 instead of chapter (the previous chapter would be
chapter 2. Sitemap components), I can't find any mention of a login tag.
In section 3.2 there is a paragraph that reads:
"This redirect-to document is an unprotected document in the sitemap. For
tracking which document was requested, the redirect-to document gets the
request parameter "resource" with the value. In addition, all parameters
specified inside the redirect-to tag of the handler configuration are passed
to the document."
First, I assume the second sentence should end with "the value of the
redirect-to uri attribute".
Second, I am confused by the last sentence of the paragraph. It leads me to
believe I should code:
<handler name="unique">
<redirect-to uri="cocoon:loginpage">
<map:parameter name="parm1" value="value1"/>
</redierct-to>
</handler>
However, I see no examples coded like this. I assume something else is meant
here.
Thanks,
Ralph
> -----Original Message-----
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 13, 2003 10:47 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Authentication Components
> >
> The authentication framework makes all information about a user, like
> e.g. the role available in the sitemap via the actions.
> You can then simply use the parameter selector to test a
> value provided
> by the auth-protect action against a value.
>
>
> Carsten
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
