This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/discussion/do/listPosts/projects.ggf-editor/discussion.rec_secure_addressing_profile_1.topc4181 at Thu, 03 Nov 2022 23:20:54 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: Editor     Discussion > REC:Secure Addressing Profile 1.0 > Refine granularity of policy attachment  > List of Posts
Forum Topic - Refine granularity of policy attachment : (2 Items)
View:  as 
 
 
Refine granularity of policy attachment
Currently, section 5.1 of the profile specifies that policy documents are to be bound to WS-Addressing actions using the
 follwing URI format: "urn:wsaaction:<wsa-action>".  (E.g., "urn:wsaaction:list", "urn:wsaaction:CreateActivity", "urn:
wsaaction:*", etc.).

However, other attachments schemes (such as WSDL attachment) allow for the policies specified in "Secure Communication" 
to be bound at the message-granularity (e.g., binding the "UsernameToken" policy to the "listRequest" input message).  

I'm suggesting we slightly alter the URI format to allow the binding of security policy to input/output/fault messages, 
(or any combination thereof): "urn:wsaaction:<wsa-action>[:<input|output|fault>]".  For example:

Bound to all messages for the list action:
   "urn:wsaaction:list"

Bound to all input messages for all actions:
   "urn:wsaaction:*:input"

Bound to all output & fault messages for the list action:
   "urn:wsaaction:list:output|fault"
Re: Refine granularity of policy attachment
Resolution: concluded it was not in the profile's best interest to alter this mechanism (and introduce new syntax or 
syntax from other specs, e.g. WSDL)

-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/discussion/do/listPosts/projects.ggf-editor/discussion.rec_secure_addressing_profile_1.topc4181 at Thu, 03 Nov 2022 23:20:55 GMT