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!
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.
“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
You’ll find me in my office. I’ll probably be drinking. And reading this tiny ad.