working with 2.0.1 code this cannot be done:
the LoginConstant session attributes are not available after successful
login:
- The normal jetspeed pipeline is executed during the login process
after the execution of the LoginRedirectorServlet
- the session attributes are deleted by the LoginRedirectorServlet
- the subject in the request, after successful login, correspond to the
principal
Joachim
David Sean Taylor wrote:
> Joachim Müller wrote:
>> Hi.
>>
>> I need to do some initialization stuff right after the login. Is there
>> an simple way to do this?
>>
>> Otherwise I would propose to introduce a LoginPostProcessValve inside an
>> after-login-pipline and execute this in the LoginRedirectorServlet
>> (similar to the login-pipeline execution in the LoginServlet).
>>
>> Any thoughts?
>>
>> (I am looking at the codebase 2.0.1)
>>
>> Joachim
>>
> Have you seen the loginValidationValve?
> You could do something similiar
> Use the loginValidation as a template to write your own
> It short circuits on the user principal being avail
> and then a session var:
> if ( request.getRequest().getUserPrincipal() == null )
> {
> if ( request.getSessionAttribute(LoginConstants.RETRYCOUNT) != null )
>
> if you have a user principal, implies a login was successful
> whereas the Subject can hold the guest(anon) user
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
. frankfurt am main, 19°c, zur zeit ein wenig
bewölkt in 213 m. die sichtweite reicht 9.0 km.
< joachim müller
[EMAIL PROTECTED]
t +49 69 759003 11
wemove digital solutions GmbH
www.wemove.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
