You are viewing a plain text version of this content. The canonical link for it is here.

Posted to rampart-c-dev@ws.apache.org by "Russell Tempero (JIRA)" <ji...@apache.org> on 2009/10/27 03:53:59 UTC

[jira] Updated: (RAMPARTC-137) When SignSupportingToken (UserNameToken) is used with transport binding, server expects a signature.

     [ https://issues.apache.org/jira/browse/RAMPARTC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Russell Tempero updated RAMPARTC-137:
-------------------------------------

    Attachment: rampart_context.c.diff

Patch to support UsernameToken assertion in a SupportingTokens assertion.

> When SignSupportingToken (UserNameToken) is used with transport binding, server expects a signature. 
> -----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPARTC-137
>                 URL: https://issues.apache.org/jira/browse/RAMPARTC-137
>             Project: Rampart/C
>          Issue Type: Bug
>          Components: Rampart-core
>    Affects Versions: Current
>            Reporter: S.Uthaiyashankar
>            Assignee: S.Uthaiyashankar
>             Fix For: Next Version
>
>         Attachments: rampart_context.c.diff
>
>
> If it is transport binding, UserNameToken should be signed by underlying transport binding. Server should not expect a signature for user name token. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.