RE: [ws-sx] More interop scenario document issues

I have not addressed any of these in the most recent update. I’ll try to hit most of these in the next one. Prateek, there is one comment I think you could better address.

From: Vijay Gajjala
Sent: Tuesday, July 11, 2006 6:35 PM
To: ws-sx@lists.oasis-open.org
Cc: Marc Goodner; prateek.mishra@oracle.com
Subject: [ws-sx] More interop scenario document issues

Browsing through the current interop scenario document, here are some issues to be fixed/need clarification:

1. I believe we are using SOAP 1.1 only for the interop. There are still places where we reference SOAP 1.2 (WSDL for example). We should fix the examples to use SOAP 1.1.

MG: Next pass.

2. Scenario 2 requires issuance of a bearer token between the STS and the client and talks of a proof of possession between the client and the service. There will be no proof of possession in this case. The client to service interaction should indicate a different binding = one that doesn’t require proof of possession.

MG: Prateek, can you take this one?

3. Editorial - Scenario 3 talks of using WSS 1.0 but has reference to X.509 token 1.1 in the client to STS binding

MG: I will work with Vijay to update this on next pass.

4. Editorial - The links in the document to the soap and addressing namespaces are broken

MG: I’m not seeing this problem. Are you sure?

Thanks

Vijay

ws-sx message