This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.ggf-editor/discussion.rec_secure_communication_profile.topc4182 at Sun, 06 Nov 2022 09:02:56 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: Editor     Discussion > REC:Secure Communication Profile 1.0 > Comments on SignedParts for X509 policy > List of Posts
Forum Topic - Comments on SignedParts for X509 policy: (2 Items)
View:  as 
 
 
Comments on SignedParts for X509 policy
We should do away with the "RequestPolicy" and "ResponsePolicy" subpolicies and just make one, unnamed policy that 
requires signature over the body and WS-Addressing headers.  

Doing so enables us to bind this policy at the level of WSDL messages (e.g., input/output/fault messages, instead of 
WSDL operations).  This is also good because we get rid of the assignment of semantics to specifically-named subpolicies
.  (For anyone who might be concerned: binding of such policy at the operation-level is acceptible for response messages
 that don't include WS-Addressing headers: WS-SecurityPolicy has "if these elements are present, you should sign them" 
semantics.)
Re: Comments on SignedParts for X509 policy
Resolved as suggested.

Duane

 
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.ggf-editor/discussion.rec_secure_communication_profile.topc4182 at Sun, 06 Nov 2022 09:02:56 GMT