Trouble with Sun One 7 and JAAS

Question

Guys,
I've been having a trouble with JAAS and Sun One 7:
- An user1 logins at application and then, open an authorized page;
- After x minutes (expressed in session-config web.xml tag), login page is automatically loaded;
- At this time, an user2 (with another profile) logins in the same app, after expired session from user1.
So, what's happening? User2 can access the same page User1 had accessed, but User2 is more restrictive than User1, so, he couldn't access the resource.
Please, help me, I don't know what to do.
Thank u,
Evandro.

Answer 1

Hi
If you want to send messages around an application using the embedded S1MQ message broker, the trick is that -- in general -- you must create the message destinations on the broker as a separate step from configuring the appserver. Then you tell the appserver how to bind a JNDI name to the destination on the broker. To create the destination on the broker, you can use the imqadmin tool (which is part of the message broker, and not the appserver). You can create both queues and topics this way. Let's suppose you created a queue called `fred'. Then you need to bind a JNDI name to this queue on the appserver.:
asadmin create-jms-resource user admin password somepassword resourcetype javax.jms.Queue property imqDestinationName=fred jms/fred
Then in the application server code you can get to the message queue by looking up `jms/fred' (strictly speaking, you should look up a java:comp/env name which you bind to jms/fred in your deployment descriptor, but that's another matter).
You'll need to do the same thing for the queue connection factory: create it using imqadmin, then bind it using asadmin.
You can do the asadmin stuff instead using the web-based admin console, but you can't (so far as I know) create the actual destinations on the broker this way.
I hope this helps. If it doesn't, copies of the relevant error message -- in full -- would help me.
Best wishes
Kevin