Sergey Beryozkin-2 wrote: > > ...One thing that I noticed is that you use URI patterns in the > configuration but also @Secured in the actual resource. Can it > actually work ? I'm not sure about it...Also, I'm assuming you've added a > Spring Security filter to the web.xml... > > cheers, Sergey >
Sergey and Andreas, you two have been enormously helpful and I cannot thank you enough. I believe I have resolved my main problem. I gave some more heed to Sergey's comment about using both URI patterns in the config and also the @Secured annotation, so I tried removing the @Secured and only using URI patterns. Voila, all of a sudden the Spring Security context was showing up in my service method with a proper Authentication object. This should work fine for me as I don't think it is essential that I map the security on the method level (unless I am missing something still ....?). Also, it may still be possible for me to use method level @Secured annotations if I clean up my URI patterns and make sure I am not trapping a URI more than once, but I have not yet had time to verify and test this. Dinner is on me if you guys are anywhere near NYC! Thanks John -- View this message in context: http://old.nabble.com/Is-it-possible-to-integrate-CXF-JAX-RS-with-Spring-Security-2.0.5---tp27587340p27634606.html Sent from the cxf-user mailing list archive at Nabble.com.
