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
Derek Hohls wrote:
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
Could you please elaborate on the use of a
session-expiration-aware attribute.
Thanks
Derek
[EMAIL PROTECTED] 2004/07/23 11:07:39 AM
Derek Hohls wrote:
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
Derek Hohls wrote:
Could you please elaborate on the use of a
session-expiration-aware attribute.
Yes of course,
[1] explains my goal.
I implemented a class inheriting from [2] HttpSessionBindingListener
interface and added it as a session attribute.
So when the session is killed (manually or by
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.
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
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/
