Hi, We have been trying to get the WS-AT interop endpoints at MS to accept our transaction context (example: see below). However, the other end at MS keeps
Nandana, I've heard you've been able to work past this issue. Could you please follow up (just to me is fine) to let me know what change was required in case
Hi; We've being testing following scenario with a WCF client. 1. WCF client talks to Rampart/Java STS and gets a security token back with SAML assertions 2.
Eamonn, The STS at http://131.107.153.205/trust has been down most of the day. The team responsible for this service is aware of the issue but has not yet