i can't see your stack traces
On 21/05/18 15:50, renz wrote:
Hi, I'm having trouble migrating from TomEE 1.7.1 to 1.7.5. I'm using Remote Stateless EJB over HTTPS (TomEE apps) for years with 1.7.1. On the server side, I use my own on JAAS Module (Realm and LoginModule) and SecurityService. The purpose of my JassRealm and SecurityService was to propagate LoginException throw by my LoginModule (see. http://tomee-openejb.979440.n4.nabble.com/Remote-EJB-Client-Authentication-JAAS-td4666734.html#a4666784). Now, with version 1.7.5 I'm having trouble and I'm suspecting that my SecurityService is not used anymore, since I don't see it in the stacktrace. Stacktrace with TomEE 1.7.1 : Stacktrace with TomEE 1.7.5 : As you can see, in first case "com.bar.foo.security.securityservice.FooBarSecurityService.login" is called where as "org.apache.tomee.catalina.TomcatSecurityService.login" in second one. Configuration seems to be the same with both versions : - Security Service is declared in tomee.xml and loaded at startup according to catalina.out - JaasRealm is declared using <Realm> in server.xml - I also add a login.conf to declare my LoginModule. In both case, JaasRealm and LoginModule are called as expected. Only the SecurityService is not. Is there any difference using SecurityService between TomEE 1.7.1 and 1.7.5 ? Thank you very much. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
