The security proxy mechanism is no longer supported by EJB3. In fact, it's really a deprecated mechanism for JBossAS. You have a few options.
You can add a custom interceptor by writing your own security interceptor class and deploying the interceptor by adding it to ejb3-interceptors-aop.xml. Or, as you mention, you can use the @Interceptor, @Interceptors, and @AroundInvoke annotations to add a security interceptor. Security information is available through the org.jboss.security.SecurityAssociation singleton - you can determine Principal and Credential information from there. You can also determine specific (target, method, parameters) info from the InvocationContext and also generic information via getContextData() View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952412#3952412 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952412 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
