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 "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org> on 2007/10/05 13:35:50 UTC

[jira] Resolved: (RAMPART-91) Wrong KeyIdentifierType in WSSecSignature and WSSecEncryptedKey

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

Ruchith Udayanga Fernando resolved RAMPART-91.
----------------------------------------------

    Resolution: Fixed

Applied the patch, thanks Nandana.

http://svn.apache.org/viewvc?rev=582216&view=rev

> Wrong  KeyIdentifierType in WSSecSignature and WSSecEncryptedKey
> ----------------------------------------------------------------
>
>                 Key: RAMPART-91
>                 URL: https://issues.apache.org/jira/browse/RAMPART-91
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>         Environment: JDK 1.5, Axis 1.3
>            Reporter: Nandana Mihindukulasooriya
>         Attachments: RampartUtil.patch
>
>
> When the key identifier is set in WSSecSignature and WSSecEncryptedKey, only WSS10 and WSS11 assertions are checked. But if there are requirements defined with in the Security Token Assertion (eg. <sp:RequireKeyIdentifierReference ... />), those requirements are not taken in to account.

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