RE: [ws-sx] Issue 70: Clarify relationship between extensibility model and policy intersection

["Martin Gudgin" <mgudgin@microsoft.com>]

Line 364-365 of[1] states that assertions with empty nested policy are
not compatible with assertions with no nested policy. 

This is also expressed in[2].

Gudge

[1]
http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/17889/ws
-securitypolicy-1.2-spec-ed-01-r06.pdf
[2] http://www.w3.org/Submission/WS-Policy/#Policy_Intersection


> -----Original Message-----
> From: Prateek Mishra [mailto:prateek.mishra@oracle.com] 
> Sent: 30 May 2006 06:56
> To: Martin Gudgin
> Cc: Marc Goodner; ws-sx@lists.oasis-open.org; ashok Malhotra; 
> ramana Turlapati
> Subject: Re: [ws-sx] Issue 70: Clarify relationship between 
> extensibility model and policy intersection
> 
> [MG]
> 
> >I think we discussed this a little on the call, but my 
> understanding is
> >that the service would publish a policy along the lines of;
> >
> ><sp:SupportingToken>
> > <wsp:Policy>
> >  <sp:UserNameToken>
> >   <wsp:Policy>
> >    <orcl:IncludesPassword wsp:Optional='true' />
> >   </wsp:Policy>
> >  </sp:UserNameToken>
> > </wsp:Policy>
> ><sp:SupportingToken>
> >
> >which is effectively two policy alternatives, one with and 
> one without
> >the orcl:IncludesPassword assertion.
> >
> >  
> >
> [/MG]
> 
> I guess I am still puzzled how policy intersection would work in the 
> expected fashion. If the client offered
> 
> <sp:SupportingToken>
>      <wsp:Policy>
>          <sp:UserNameToken/>
>     </wsp:policy>
> </sp:SupportingToken>
> 
> then, would policy intersection between the two would still fail?
> 
> - prateek
> 
> >  
> >
> 
>