hi,
In the commit() of the client login module I add to the subject:
subject.getPrincipals().addAll(tempPrincipals);
subject.getPublicCredentials().addAll(tempCredentials);
where tempCredentials contains the property name-value pairs:
c.setProperty("nhs number", nhsNum);
c.setProperty("customer id", custId);
The passive callback handlers PassiveCallbackHandler has constructor that takes a username and password so its handle() method does not have to prompt the user for input. This information is supplied by a JUnit test or by a jsp which gets the information from a HTML form. There is no peripheral security restrictions.
It is the custId that needs to be visible to the custom server login module.
At this time the application is deployed on my desktop running a default JBoss server.
Hope this helps. Cheers
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958514#3958514
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958514
Hello,
I have a problem with constructing a query which uses group-by and sorts by an aggregate column. As I use MySQL, I can't just write "ORDER BY min(column)", so I try a different approach, which works in MySQL, but throws an exception when I try to use it in EJB3. My query looks like this:
| SELECT name, min(dateCreated) AS mdc FROM TagEntity
| GROUP BY name
| ORDER BY mdc
|
Any ideas how can I do it any other (working :) ) way?
--
Cheers,
Adam
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958511#3958511
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958511
"mdaguete" wrote : Hi all,
| I'm usign jboss 4.0.3 in debian stable with linux kernel 2.6.8-2-686-smp in a 2x Xeon CPU with Hyperthreading, Java HotSpot(TM) Server VM (build 1.5.0_05-b05, mixed mode) and 4GB RAM, af ter a few days my application throws a "OutOfMemoryError: unable to create new native thread"
|
You may want to check if your application is leaking threads. You can actually run out of mappable process memory if you have too many threads, even though you have lots of heap still.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958510#3958510
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958510