ng
You say:
"Notice the authentication action, without it ID will not be
available."
What you can also do is store the userID in the session context
at the point of login; its then available even when the
<map:act type="auth-protect"> is not used. The only trick
is to remember to "reset" it when the logout is called...
Derek
>>> [EMAIL PROTECTED] 2004/07/22 03:52:59 PM >>>
Hi Derek,
Thank you very much for your reply. It seems like there is a neat
alternative solutions. The user name (as well as other authentication
info, like role) can be accessed by referencing the ID element:
<!-- Take submitted form and write it into the RSS file -->
<map:match pattern="addNewsItem">
<map:act type="auth-protect">
<map:parameter name="handler"
value="portal-handler"/>
<map:generate type="jx" src="updateRssQuery.xml">
<map:parameter name="userId" value="{ID}"/>
</map:generate>
<!-- map:transform type="xmldb"/ -->
<map:serialize type="xml"/>
</map:act>
</map:match>
Notice the authentication action, without it ID will not be available.
To access this parameter within the JX template use this:
...
<author>${cocoon.parameters.userId}</author>
...
However, passing user name as a request parameter is just as good.
Thank you very much once again.
Sincerely,
ng.
Derek Hohls wrote:
> Nick
>
> FWIW, I am using:
>
> ${parameters.getParameter('userID')}
>
> in my JXTemplates to get the userID, after
> it has been passed as a parameter in the
> pipelines.
>
> Derek
>
>
>>>>[EMAIL PROTECTED] 2004/07/22 05:16:44 AM >>>
>
> Hi everybody,
>
> I got stuck trying to pass the User Name into a Portal Engine
pipeline.
>
> The pipeline looks like this:
>
> <!-- Take submitted form and write it into the RSS file -->
> <map:match pattern="addNewsItem">
> <map:act type="auth-protect">
> <map:parameter name="handler" value="portal-handler"/>
>
> <map:generate type="jx" src="updateRssQuery.xml">
> <!-- map:parameter name="userId"
> value="${session-context:authentication/ID}"/ -->
> <!-- map:transform type="xmldb"/>
> <map:serialize type="xml"/>
> </map:act>
> </map:match>
>
> I can't use Session transformer to get the ID from the authentication
> context (there are chances that some of the namespace declarations
will
>
> be lost). Passing User Name as a request parameter is not very safe
> either.
>
> I am just checking if anybody has ever got access to the
authentication
>
> context within the JX template by some other means? In other words,
is
>
> there a call similar to ${cocoon.request.getParameter("blah")} that
> could grant access to the ID parameter within authentication context
or
>
> some other way to get access to the parameter?
>
> Thank you very much for your time.
>
> Sincerely,
> Nick
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
