Hi Nacho,
thank you for the replay, I tried to follow your cues but I didn't solve
it.
I tried to modify the authentication block samples sitemap as follow :
<map:pipeline>
....
<!-- ========================================= -->
<!-- Logout link which invalidates the session -->
<!-- ========================================= -->
<map:match pattern="protected/do-logout">
<map:act type="auth-protect">
<map:parameter name="handler" value="demohandler"/>
<map:generate type="serverpages" src="docs/prova.xsp">
<map:parameter name="ups" value="{request:remoteUser}"/>
</map:generate>
<map:serialize/>
<map:act type="auth-logout"/>
<map:redirect-to uri="login"/>
</map:act>
</map:match>
</map:pipeline>
and prova.xsp looks like below :
<?xml version="1.0"?>
<xsp:page xmlns:xsp="http://apache.org/xsp"
xmlns:xsp-request="http://apache.org/xsp/request/2.0"
xmlns:util="http://apache.org/xsp/util/2.0">
<page>
<xsp:logic>System.out.println("prova.xsp"+<util:get-sitemap-parameter
name="ups"/>);</xsp:logic>
</page>
</xsp:page>
but in the output of the console I'm not able to find the user ID.
May you help me find where I mistake ?
thanks a lot
Flavio
>-- Original Message --
>Reply-To: [EMAIL PROTECTED]
>Date: Wed, 12 May 2004 12:03:55 +0100
>From: Nacho Jimenez <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: retrieve user in logout action
>
>
>Flavio Palumbo wrote:
>
>>Hi all,
>>
>>forgive me for the quick repost, but I'm getting crazy to figure out how
>>retrieve the user ID that is currently doing logout from the authentication
>>framework.
>>I'd like to get it in a custom action, called just before auth-logout
action,
>>because I need to update some Db tables based on the user ID.
>>
>>
>>
> Protect the pipeline with the logout action (nesting it with the
>auth-protect action). That way, you can acccess the Authentication
>session context via the input module, and pass the parameter to your
>action from the sitemap.
>
> If your action is written in XSP, you can also use the session-fw
>logicsheet to get the username from /authentication/ID, but again, it
>has to be protected.
>
> Hope that helps
>
>Nacho
>
>---------------------------------------------------------------------
>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]