W3C home > Mailing lists > Public > public-ws-policy@w3.org > July 2006

RE: NEW ISSUE: HTTP/HTTPS conflict resolution between policy assertion and WSDL

From: Ashok Malhotra <ashok.malhotra@oracle.com>
Date: Tue, 18 Jul 2006 04:59:14 -0700
To: "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <20060718045914128.00000002312@amalhotr-pc>
I wonder if this isn't an example of a more general problem where the policy and the capabilities of the transport conflict. Specifically, if the policy requires a capability that the transport cannot provide or a capability the transport already provides.  Consider a policy that requires reliable messaging. If this policy is used with MQ as the transport what happens? Does the engine recognize that MQ already provides reliable messaging and ignores the assertion or does it try and build reliable messaging on top of MQ? 
All the best, Ashok 
From: public-ws-policy-request@w3.org [mailto:public-ws-policy-request@w3.org] On Behalf Of Toufic Boubez Sent: Monday, July 17, 2006 10:02 PM To: public-ws-policy@w3.org Subject: NEW ISSUE: HTTP/HTTPS conflict resolution between policy assertion and WSDL Title - HTTP/HTTPS conflict resolution between policy assertion and WSDL  Description - If the security policy assertion requires the use of HTTPS transport level security and WSDL port address uses HTTP scheme, what is the best practice guidance for requestors?  Target - WS-Policy Attachment 1.5? Primer?  Proposal - Not sure if I have an absolute proposal, but I'll get the ball rolling: I propose that if there is a conflict, that since presumably the policy authors are a better authority as to what policies should exist for a service, whereas the WSDL might have been automatically generated by a tool or a developer, the policy assertion takes precedence.  Toufic Boubez, Ph.D. Chief Technology Officer LAYER 7 TECHNOLOGIES / Advancing the application network. 604.681.9377 x310 (w) 604.288.7970 (m) tboubez@layer7tech.com (e) www.layer7tech.com (w)
Received on Tuesday, 18 July 2006 11:59:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:38:26 UTC