John Smith

+ Follow
since Dec 12, 2005
Merit badge: grant badges
For More
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by John Smith

There are examples of doing almost everything in your installation examples directory. Last time I checked, there were about 90 example pages illustrating all the techniques.

Run examples/grid/edit-grid.html

And read the API docs, and join
This gets the URL:

URL myURL = Thread.currentThread().getContextClassLoader().getResource("persistence.jar");
I have several modules in my EAR file.

I'm wondering how I can get access to the modules specified in my application.xml descriptor.

I have for example,

<ejb id="persistence.jar">persistence.jar</ejb>

How can I access that jar as a resource in a standard way? Is it on the classpath of any ClassLoader that I can access?
OK, I've found it:

in my JAAS LoginModule:

So, I can pull the LogniModule out of the session anywhere, and see if any URL is going to be allowed.
18 years ago
Well, after much searching, I randomly stumbled across the correct incantation to be able to log out using session.invalidate():

in jboss-web.xml

So now, I can log out when they click the logout link.


Next up, how to programatically determine whether a URL is available to the current user.

I'm of course using container-managed authorization, but it's no good outputting a link only to have the user click on it, and be tipped into the error page by JBoss. I want to have a custom tag for links which does not output any HTML if the URL is not accessible to the current user.

Any ideas?

[size=9]No doubt, I'll find the incantation at some random site given enough searching...[/size
18 years ago
Someone else suggested this to me, so I tried it.

Calling session.invalidate() does not cause the container to invoke the logout() method of my LoginModule. Even though the container called the login() and commit() methods.

This is a really strange omission. Surely, there is a way to explicitly request the container to log the current session out. The container surely maintains the LogniContext object somewhere!?

(Thanks for your help on this by the way...)
[ December 21, 2005: Message edited by: John Smith ]
18 years ago
That really saved our bacon, and we're back on track.

One problem though.

The web app does not have access to the that JBoss created to perform the login.

So it cannot explicitly log out!

How does any JAAS-secured web app under JBoss ever log out?
18 years ago
Well spotted. I've been looking through the wiki, but unless you know what you are looking for, then finding it is pretty difficult.

Well, it works like a charm!

HOw on earth did you find that incantation? I've been harassing the posters on the forums for a week now, and nobody, not even the JBoss developers came up with anything!
18 years ago
Nobody has any ideas???

This is a common situation - a lot of places use more than just username/passsword.

I need access to the HttpSession in my LoginModule.
18 years ago
I have a LoginHandler which is being called by JBoss to authenticate the login form.

The problem is, that it needs more information from the form than just the j_username and j_password.

It also needs a "company name" parameter too.

Also, it realy needs some parameters from the originally requested URL which specify some back end server details to enable the connection and login to take place. The connection to the server is cached in the HttpSession.

I can't see how to do this. An unlogged in request is intercepted before any declared Filters, and JBoss's CallbackHandler only accepts UsenameCallback, and PasswordCallback.

Before, when I used a Filter to control access, I set up my own CallbackHandler to pass into the LoginContext which accepted new subclasses of Callback so it provided access to the HttpSession (and therefore all attributes in it), so the LoginModule could do anything.

With container-managed authentication, all you get is the username and password. How can this be adequate in 100% of cases?! It's just not good enough!
18 years ago
Thanks for that topic. The magic incantation seemed to be

in jboss-web.xml which actually made it use

in login-config.xml. This is not explained anywhere. Did this technique evolve? Did someone randomly hit on this?

Anyway. OK so far, but my login module needs more information from the login form than just the j_username and j_password which are available from JBoss's CallbackHandler.

I need JBoss to use my custom CallbackHandler to get info out of the HTTP request. This accepts another Callback subclass, a CompanyNameCallback. This is needed to perform our login method.

Anyone know, how I can obtain more information from the login form?

[ December 12, 2005: Message edited by: John Smith ]
[ December 12, 2005: Message edited by: John Smith ]
18 years ago