locked
w2k8r2 CES/WSTEP - WSDL appears incomplete RRS feed

All replies

  • I wouldn't look at the mex output to determine the correct wsdl. I don't think that is supported by the Microsoft CES web service.

    Have a look at: http://msdn.microsoft.com/en-us/library/dd357987(v=PROT.13).aspx

    In appendix 6, it indicates that WSTEP is a profile extension of WS-Trust 1.3 which does include operations in portType.

     

    Andrew

    Thursday, July 28, 2011 8:44 PM
  • Hello,

    I was able to get requests over CES working. I had to use the standard WS-Trust 1.3 WSDL hosed by OASIS in order to do so. The WSDL that CES returns if you enable the metadata is of no value.

    The actions in the standard WSDL also don't match what Microsoft's service is requesting however, so I also had to change those to match. Looking at the example in 4.1.1.1 here should help. Specifically, the http://schemas.microsoft.com/windows/pki/2009/01/enrollment/RST/wstep action was needed on the SecurityTokenService.RequestSecurityToken2. Note there are two sets of methods in the WS-Trust spec, and the first set is useless. You will need to call the RequestSecurityToken2 method for a collection to be returned. That part is also not well documented.

    You may not see this, but I wanted to leave this here in case someone else has the same problems. There doesn't seem to be anyone else saying they've successfully utilized CES yet, and I know I struggled with it quite a bit before having success. The biggest help was to enable client-side logging and making the XML request match Microsoft's MSDN example linked above.


    • Edited by npnance Thursday, February 23, 2012 2:11 AM
    Thursday, February 23, 2012 2:05 AM