Hi Colm. In collaboration with the STS side we have gathered a package of files that you can see below.
Here are the logs from the .NET stack. Client name is Agent and Service name is BookingService. *WCF Client*: http://cxf.547215.n5.nabble.com/file/n5711830/Agent_-_WCF-ML.svcLog Agent_-_WCF-ML.svcLog *WCF Service*: http://cxf.547215.n5.nabble.com/file/n5711830/BookingService_-_WCF-ML.svcLog BookingService_-_WCF-ML.svcLog All logs from .NET are produces through WCF Logging mechanism. They are a bit difficult to read without "Microsoft Service Trace Viewer". Here are the logs and wsdl file that the STS side sent me: *Catalina Log*: http://cxf.547215.n5.nabble.com/file/n5711830/catalina.2012-08-01.log catalina.2012-08-01.log *Logging Properties*: http://cxf.547215.n5.nabble.com/file/n5711830/logging.properties logging.properties *Endpoint configuration*: http://cxf.547215.n5.nabble.com/file/n5711830/cxf-transport.xml cxf-transport.xml *ws-trust-1.4.wsdl*: http://cxf.547215.n5.nabble.com/file/n5711830/ws-trust-1.4.wsdl ws-trust-1.4.wsdl *ws-trust-1.4-service.wsdl*: http://cxf.547215.n5.nabble.com/file/n5711830/ws-trust-1.4-service.wsdl ws-trust-1.4-service.wsdl *FedizSTS Standard Output*: http://cxf.547215.n5.nabble.com/file/n5711830/FedizSTS_StandardOutput.txt FedizSTS_StandardOutput.txt NET Client is using the fedizidpsts/TPUT endpoint Thank you again for your time and efforts -- View this message in context: http://cxf.547215.n5.nabble.com/WS-Trust-Version-and-WCF-tp5711662p5711830.html Sent from the cxf-user mailing list archive at Nabble.com.
