aspose file tools*
The moose likes Servlets and the fly likes How do this? (Own type of login, but associate with container)? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "How do this? (Own type of login, but associate with container)?" Watch "How do this? (Own type of login, but associate with container)?" New topic
Author

How do this? (Own type of login, but associate with container)?

Robert Paris
Ranch Hand

Joined: Jul 28, 2002
Posts: 585
I want to define my own login method (i.e. there's the built-in form-login which uses j_security_check for example). How would I do this? Is there a J2EE standard for this?

I originally was OK with using j_security_check because I thought I could put a filter on it (I need to hash the password passed in for comparison to the hashed password in the database), but that's not possible. Ideally I want to require a certificate and username and password (and I'll hash the password) but I can't do this with built-in J2EE security (WHY?! it wouldn't have been hard to make a generic interface that gave flexibility). Anyone know how I would do this?

I know how to get the user/pass, etc but I don't know how to associate it with the container - which is the big hang up here. I want to be able to tie it in. Argh!

Thanks!
Bug Menot
Greenhorn

Joined: Oct 15, 2004
Posts: 26
have you tried using Realms?

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/realm-howto.html
Robert Paris
Ranch Hand

Joined: Jul 28, 2002
Posts: 585
yeah, but it's non-portable across containers. I'm really dissapointed by the poor security api for web apps in java.
Paul Bourdeaux
Ranch Hand

Joined: May 24, 2004
Posts: 783
Hi Robert,

You are right in that implementing a JAAS module tends to be rather container specific. Usually you have to extend a container provided login module class instead of implementing LoginModule yourself. This can be frustrating when you are working on a more global solution.

There are two ways I can think of around this.

1) Develop a business class that performs the authentication work, and build caller classes that extend the classes provided by the container but call the business class to do all of the work. This way you can keep all of the logic out of the container specific code. This will also give you the flexibility to change the type of authentication (i.e. jdbc, ldap...) at run time if you use a factory. This solution, while useful, can also be quite complex and time consuming.

2) Have you considered using a client side hash instead? I faced the same problem you did in a project, and chose instead to hash the password using a JavaScript function before sending it across the network. This way I could still use the j_security_check if I wanted to.


“Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.” - Rich Cook
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: How do this? (Own type of login, but associate with container)?