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

Posted to rampart-dev@ws.apache.org by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org> on 2007/10/26 10:27:50 UTC

[jira] Updated: (RAMPART-100) Missing encrypted key token in response when Asymmetric Binding is used

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

Nandana Mihindukulasooriya updated RAMPART-100:
-----------------------------------------------

    Attachment: MutualCertificate10SignEncrypt_IPingService_Response.xml
                client2-policy.xml

Asymmetric binding policy used and the response soap message.

> Missing encrypted key token in response when Asymmetric Binding is used
> -----------------------------------------------------------------------
>
>                 Key: RAMPART-100
>                 URL: https://issues.apache.org/jira/browse/RAMPART-100
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.3
>            Reporter: Nandana Mihindukulasooriya
>            Assignee: Nandana Mihindukulasooriya
>         Attachments: client2-policy.xml, MutualCertificate10SignEncrypt_IPingService_Response.xml
>
>
> When asymmetric binding policy is used and  rampart uses the same encrypted key token used in the request to do the encryption in the response.  But in asymmetric binding, we should use a new encrypted key token created using initiators public key. 

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