[
https://issues.apache.org/jira/browse/RAMPART-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Vladov updated RAMPART-181:
----------------------------------
Attachment: rampart-core_configbuilder.txt
Sorry it seems the previous patch generated by eclipse included the project
name as well (since it was relative to my workspace... )
Indeed it seems the decryption crypto is not used - when the rampart engine
calls the WSSecurityEngine#processSecurityHeader it passes the encryption
crypto config to be used for decrypting the message...
> OptimizePartsConfig does not open namespace tag when serializing the assertion
> ------------------------------------------------------------------------------
>
> Key: RAMPART-181
> URL: https://issues.apache.org/jira/browse/RAMPART-181
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Assignee: Ruchith Udayanga Fernando
> Priority: Minor
> Fix For: 1.4
>
> Attachments: rampart-core_configbuilder.txt
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> In rampart-core org.apache.rampart.policy.model.OptimizePartsConfig, when
> serializing the list of namespaces the xml stream writer forgets to open the
> namespace tag and the serialize methods naturally throws a
> XMLStreamException... not that I will ever use this... just noticed it
> accidentally :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
