OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-sx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


Scott, what Symon is saying is for the already defined token profiles in WSS, so this is a confined space.

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Inactive hide details for "Scott Cantor" <cantor.2@osu.edu>"Scott Cantor" <cantor.2@osu.edu>


          "Scott Cantor" <cantor.2@osu.edu>

          02/17/2006 12:31 PM


To

"'Symon Chang'" <schang@bluetitan.com>

cc

<ws-sx@lists.oasis-open.org>

Subject

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

> Our position would be the same: all properties in WSS Token
> Profiles should be expressible within WS-SecurityPolicy.
> UserName Token Profile is just one of good examples to show
> the need of such granularity of policy requirement.

One has to allow for the fact that this is impossible in the sense that
anything can be a WSS Token. There's no way to capture all the
possibilities.

So I assume the goal is to facilitate the creation of WS-SecurityPolicy
token profiles. As there probably is in just about every one of these specs.
This may already be possible in the current schema, but if not, that would
be the thing to correct.

-- Scott


GIF image



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]