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 2008/04/02 05:13:25 UTC
[jira] Commented: (RAMPART-147) Header parts included in
EncryptedParts are not processed by Rampart
[ https://issues.apache.org/jira/browse/RAMPART-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584385#action_12584385 ]
Nandana Mihindukulasooriya commented on RAMPART-147:
----------------------------------------------------
Hi Miguel,
What is the revision you are referring to. In Rampart 1.3 we didn't support Encrypted Headers. And in the trunk , that line is there.
https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy11/builders/EncryptedPartsBuilder.java
thanks,
/nandana
> Header parts included in EncryptedParts are not processed by Rampart
> --------------------------------------------------------------------
>
> Key: RAMPART-147
> URL: https://issues.apache.org/jira/browse/RAMPART-147
> Project: Rampart
> Issue Type: Bug
> Components: rampart-policy
> Affects Versions: 1.3
> Reporter: Miguel Arauzo
> Assignee: Ruchith Udayanga Fernando
>
> The method 'processElement' from class org.apache.ws.secpolicy.builders.EncryptedPartsBuilder doesn't add the 'sp:Header' elements to the SignedEncryptedParts instance:
> private void processElement(OMElement element, SignedEncryptedParts parent) {
>
> QName name = element.getQName();
>
> if (HEADER.equals(name)) {
> Header header = new Header();
>
> OMAttribute nameAttribute = element.getAttribute(NAME);
> if( nameAttribute != null ) {
> header.setName(nameAttribute.getAttributeValue());
> }
>
> OMAttribute namespaceAttribute = element.getAttribute(NAMESPACE);
> header.setNamespace(namespaceAttribute.getAttributeValue());
>
> <<== The following code is missing: parent.addHeader(header);
> } else if (BODY.equals(name)) {
> parent.setBody(true);
> }
> }
> The result from this "missing line of code" is that it's impossible to process a message that has some encrypted element besides the SOAP body.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.