TomEE realm should just wrap the invocation of authenticate method to do some init in case of a good login so your setup seems ok Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2013/12/16 renz <[email protected]>: > I've tried a few customization by : > - creating a FooBarJAASRealm extending JAASRealm > - implementing my own SecurityService, FooBarSecurityService to fetch > exceptions thrown by FooBarJAASRealm.authenticate() exceptions, since Realm > interface doesn't allow authenticate() to throw any LoginException > > Now my problem is that the FooBarSecurityService doesn't access directly to > an instance of FooBarJAASRealm but to an instance of TomEERealm containing a > FooBarJAASRealm (which is not accessible). > > Am I on the right way? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Remote-EJB-Client-Authentication-JAAS-tp4666734p4666770.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
