Re: [wss-comment] recursive Security Token References

[Ron Monzillo <Ronald.Monzillo@Sun.COM>]

Conor P. Cahill wrote:
> 
> Anthony Nadalin wrote on 9/1/2005, 11:12 AM:
> 
>  > Thanks for the explanation, given this description it looks like you
>  > are looking for more of a general token carrier (bag-o-tokens) and not
>  > a reference mechanism. The STR was not designed as a bag-o-tokens but
>  > a means referencing tokens and key material that can't be referenced
>  > otherwise (as they may have closed content model).
> 
> I find this statement quite interesting given the fact that you cant use
> an STR to refer to an STR and the common solution is to have the second
> STR refer to the token in the embedded element (which would mean that
> you do have a "means of referencing such tokens and key material" ).
> 
> Not trying to be argumentative, just pointing out that on one hand the
> WSS TC is saying that STRs are there to deal with tokens that can't be
> directly referenced for whatever reason and on the other hand saying
> that another STR will somehow find a way to directly refer to such tokens.
> 

I agree that there is an inconsistency if one uses an embedded STR
as a means of referencing tokens and key material that can't be
referenced otherwise. I think wss could do without embedded STRs.


> Conor
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wss-comment-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wss-comment-help@lists.oasis-open.org
> 

--