Hi
On 25/07/15 16:34, jsmith828 wrote:
Thanks Sergey! Yes I ran the test through the NB debugger breaking on the
throwFault method and was able to see that the original exception was
"Cannot create a secure XMLInputFactory". I tried a few things with my POM
after reading this article
(http://stackoverflow.com/questions/20114945/cxf-web-service-client-cannot-create-a-secure-xmlinputfactory)
to see if I could get rid of it but I didn't have any luck. I am using CXF
3.1.0 and I overrode my woodstox-core-asl to use 4.2.0 but that didn't work
either. Again I am using tomcat and I did not see any specific instructions
for getting rid of this issue on tomcat. To get around it I set:
-Dorg.apache.cxf.stax.allowInsecureParser=1
which I understand is not a safe solution. Any help here is most
appreciated!
I think in your case it should be fine, you have HTTPS, the actual
payload is JSON, and the assertion creation is under your control.
Though I'm not sure why woodstox can be recognized in Tomcat - I did run
few demos in Tomcat recently (I think...). What do you mean "my version
of woodstox...", it should usually be in your CXF-based war ?
Cheers, Sergey
Thanks
-Jeff
--
View this message in context:
http://cxf.547215.n5.nabble.com/Getting-a-server-error-trying-to-read-SAML-assertion-tp5759446p5759450.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
