RE: [wss-comment] recursive Security Token References

[Anthony Nadalin <drsecure@us.ibm.com>]

Referencing tokens is different than referencing the referencing mechanism to reference tokens, the STR is there as a means to reference tokens that closed content models, so it solves the issue of being able to reference a security token.

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
"Conor P. Cahill" <concahill@aol.com>

"Conor P. Cahill" <concahill@aol.com>

09/01/2005 10:30 AM

To	Anthony Nadalin/Austin/IBM@IBMUS
cc	"Tech Rams" <techmailing@yahoo.com>, "DeMartini, Thomas" <Thomas.DeMartini@CONTENTGUARD.COM>, wss@lists.oasis-open.org, wss-comment@lists.oasis-open.org
Subject	RE: [wss-comment] recursive Security Token References

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.

Conor