Hello,
I'm working on an application that has until now primarily used Lift
for the mapper framework (1.1-M8). This includes us extending Meta/
MegaProtoUser to get the basic user account functionality while
rolling our own servlets and front-end client (not using Lift).
Now we want to make use of the Lift ProtoUser views and functionality
for reset password, lost password, etc. I've tried including calls to
User.actionsAfterSignup and User.logUserIn from our own signup/signin
service methods so that those included forms will be in-sync with the
login status of our application.
The problem is that calls to logUserIn and actionsAfterSignup don't
appear to do anything. User.currentUserId is always Empty and
navigating to the /user_mgt/login page does not redirect as if the
user is logged in, unless I specifically login through those created
pages.
How can I hook our own signup/signin logic up to be in sync with the
ProtoUser functionality?
Thanks for any pointers!!
dave
For example, our signup/signin service methods went something like
(simplified):
def signUp(...) = {
val user = User.create.email(email).password(password)
user.validate match {
// ok to save/create
//user.save // old approach
User.finalizeSignup(user) //--> defers to
User.actionsAfterSignup(user)
}
}
def signIn(...) = {
User.findByUsername(username) match {
case Full(user) if (user.password.match_?(password)) => {
// log user in
// ...
User.logUserIn(user)
}
}
}
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
