Link to home
Start Free TrialLog in
Avatar of R_a_V_e_N
R_a_V_e_N

asked on

Implementing logout with BASIC Security

Hi,

I have implemented BASIC security for my assignment. I defined Users and Groups in Weblogic and then defined roles and allowed users in Deployment descriptor.

Now I have found out that I have to implemnet log out as well. I was wondering if there is any way I could achieved this using BASIC security? It doesn't have to be complicated, as long it does the job!

If there is not a way, should I change all my security structure to use Forms or there is some hybrid possible with Forms and BASIC security?

Thanks for you're help!
Avatar of jimmack
jimmack

I thought that this happened when you invalidated the session using HttpSession.invalidate().
Avatar of R_a_V_e_N

ASKER

I don't think so.
Sorry Raven ;-)

I found this though.  It may help :-)

http://groups.yahoo.com/group/jrun-interest/message/9534
Thanks for your help jimmack!

But I still don't think this will work. This is more related to forms security. Following is the copy & paste from the site you gave:

e.g..
1) user click on link to jsp page
2) jsp page invalidates the session
3) jsp page creates a new session
4) set the flag in session
5) when the user tries a protected link...
a) get session
b) check for flag
c) .. if it is there deny and unset flag
d) other wise do normal validation stuff

This will force the browser to reprompt for user name and password. NOTE ie will show login screen netscape will say login attempt failed and as if they want to retry

I understand upto 5b, but 5c and 5d don't make sense to me. If I unset the flage how will it force the browser to redisplay login page? Also, what exactly is meant by deny?

Thanks for your help!
Sorry for the late response.  I've had two frustrating days of not being able to resolve the EE URL :-(

You are right, 5c and d are not exactly "clear" ;-) and it does seem to use the same session invalidation that is more applicable to form based security.

I think I need to dig out my "More Servlets and JSPs" book to find out more about how basic security manages the login info.  (My first comment was based on the idea that it would be via the session).  Obviously there must be something stored somewhere that becomes invalid at some stage, otherwise a user would always have access when they've logged in once :-)

I'll go hunting for my book when I get chance (unless you can already explain it.  That might save time ;-)).
"...and that it is very difficult to log in as a different user once you are authenticated. In fact, once authenticated, you have to quit the browser and restart if you want to log in as a different user! Now, in principle it is possible to write a “relogin” servlet that sends a 401 Unauthorized status code and a WWW-Authenticate header containing the appropriate realm. But, that is hardly “declarative” security!"

Thats from More Servlets and JSPs. Actually, FORMs security is not difficult as I first thought. It is almost same as this, except I have to provide Login and Error pages.

Is this relogin servlet difficult to write? or is my best bet to change to FORMs security?

Thanks for you're help jimmack!



ASKER CERTIFIED SOLUTION
Avatar of jimmack
jimmack

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
fair enuff, forms are quite easy!

Thanks for you're help :)))
No problem.

Have fun ;-)