JIT Login (WPO) and DirectAction component
JIT Login (WPO) and DirectAction component
- Subject: JIT Login (WPO) and DirectAction component
- From: Erwin <email@hidden>
- Date: Tue, 5 Apr 2005 10:20:43 +0200
A little bit different from what I read in WPO, I implemented my JITLoginPage as a stateless page
I check the login and the password in this page (row fetched) ,
then I refetch the user object from the Session defaultEditingContext,
AbstractUser authenticatedUser = (AbstractUser) EOUtilities.objectMatchingKeyAndValue(session().defaultEditingContext(), "AbstractUser", "login", userLogin);
then I create the session
session().takeValueForKey(authenticatedUser, "authenticatedUser");
It's there (I can print it)....
My destinationUrl is right (as stated in WPO), and after the identification process the transfer is done to the destination page (ArchivePage, also stateless component) where I put :
public void appendToResponse(WOResponse response, WOContext context){
if ( ! ((Session)session()).isUserAuthenticated()){
WORedirect loginPageRedirect = (WORedirect) pageWithName("WORedirect");
loginPageRedirect.setUrl(DirectAction.secureLoginUrl(context));
loginPageRedirect.appendToResponse(response, context);
} else {
super.appendToResponse(response, context);
}
}
Unfortunatly :
((Session)session()).isUserAuthenticated() always returns FALSE...
Even if I try to check it with :
session().valueForKey("authenticatedUser")
I always got a null value, so there is again a redirect to the JITLoginPage ...
my session component is the 'standard' WPO session (used in chap 4)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden