RE: [ws-sx] Issue 31: Clarification for UsernameToken assertion

> [MJG]
> The client needs to be able to construct a token that matches 
> the token profile in use. 
> 
> If the token profile allows for variation, then the client 
> can choose to send any token that matches the profile and the 
> service should accept it.
> 
> Do you have a specific scenario in mind where a service only 
> supports a subset of a WSS Token Profile?

How about any scenario involving a SAML assertion as a token? If you have no
granularity other than "token type", then is there a bucket of <any> in
there for some other profile to define?

-- Scott