I apologize for asking a question that I could answer myself with a few more 
hours of study...

I need to do some rudimentary username/password checking on a Webware site.  I 
would like to have two or three classes of users with different authorizations.

I believe that UserKit can help me achieve this, but I can't seem to grasp the 
10,000 foot overview of how it hooks in.  I'm hoping someone can offer a few 
gentle words for me.

Each page will want to make sure the user has logged in before proceeding.  Do 
I need to instantiate a UserKit object in every class, then?  Is the usual 
procedure to derive a class from UserManagerToFile and use that class in every 
servlet?  Does UserKit manage the session cookie for maintaining the user name?  
I'm using OneShot.cgi right now because the site is dynamic.  Does the 
persistance still work in that case?

I need to write the login page myself, right?  How do I force the login page to 
pop up if they aren't logged in?  self.response.sendRedirect()?

Is there a wiki set on UserKit?

--
- Tim Roberts, [EMAIL PROTECTED]
  Providenza & Boekelheide, Inc.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to