To be a little clearer,
function authenticate_user()
{
var user = service.authenticateUser(cocoon.request.get("username"), cocoon.request.get("password"));
if(user!=null){cocoon.session.setAttribute("user", user);cocoon.session.setAttribute("loggedIn", "true")}
cocoon.sendPage("internal/xml-user", {user : user});
}
the "internal/xml-user" is what generates teh xml for the auth-fw
service is a java class I use to handle all the methods of my own user/role management.
JD Daniels wrote:
I wrote my own user/role beans and use them in the auth fw. when the login is successful, i just store the bean in the session and use it everywhere. I dont use the xml in the session much except to use the auth fw is_logged_in type stuff.
JD
Martin Rusnak wrote:
Dear all,
I use authentication framework with my own Authenticator class derived from
org.apache.cocoon.webapps.authentication.components.Authenticator.
Authenticatioin framework needs user data to be stored as XML in the session
context, but the business logic part of my application works with user bean.
Converting the XML to user bean every time the HTTP request is performed would
unnecessarily take CPU and memory resources. Therefore it would be useful to
store user bean in the session insted of XML. Is it possible to do with
authentication framework or do I need to implement the authentication myself?
Best regards, Martin
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
