[
https://issues.apache.org/jira/browse/RAMPART-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya updated RAMPART-91:
----------------------------------------------
Attachment: RampartUtil.patch
A patch with modified RampartUtil class which has a method
setKeyIdentifierType() which correctly sets the setKeyIdentifierType. Still
<sp:RequireEmbeddedTokenReference ... /> in <sp:X509Token .../> is ignored as
WSSecSignature and WSSecEncryptedKey of
WSS4J doesn't support it.
> 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.
