I tried both the patch and version 4.0.3RC1. Both end up with the same "No matching username found in Principals". Just as if the code responsible for pushing the credentials from Tomcat to the EJB container was pushing null instead of the corect value. Amazingly enough, version 4.0.3RC1 works fine when I replace Tomcat 5.5 sar by Tomcat 5.0. Of course, when you declare a run-as element for you EJBs, the caller identity will be that one instead of the one that was authenticated by the web container. This can produce different error messages, but imho these are due to the same problem in Tomcat5.5 sar. Works fine with JBAS 4.0.1SP1 as well as version 3.2.3.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883833#3883833 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883833 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
