[OASIS Issue Tracker] Commented: (IMI-26) Conflict between SAML 2.0token profile and WS-Trust

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/IMI-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821#action_16821 ] 

Scott Cantor commented on IMI-26:
---------------------------------

Proposal accepted in WD-04.

> Conflict between SAML 2.0 token profile and WS-Trust
> ----------------------------------------------------
>
>                 Key: IMI-26
>                 URL: http://tools.oasis-open.org/issues/browse/IMI-26
>             Project: OASIS Identity Metasystem Interoperability (IMI) TC
>          Issue Type: Bug
>            Reporter: Michael Jones
>            Priority: Minor
>
> The SAML 2.0 token profile currently says:
> If a token request does not include a <wst:KeyType> element, the Identity Provider SHOULD assume that an asymmetric proof key is required.
> This is contrary to the WS-Trust spec, Section 9.2 (Key and Encryption Requirements) which says that in the absence of a <KeyType> element, the key type should default to a symmetric key.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira