[
https://issues.apache.org/jira/browse/RAMPART-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644726#action_12644726
]
Richard Gibson commented on RAMPART-136:
----------------------------------------
Rampart 1.4 features:
WS Security Policy 1.2 support
However the WS-SecurityPolicy 1.2 standard
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.html
states for the RequiredElements Assertion:
"This element contains a string specifying an XPath expression that identifies
the header elements that a message MUST contain. The XPath expression is
evaluated against the S:Envelope/S:Header element node of the message. Multiple
instances of this element may appear within this assertion and should be
treated as a combined XPath expression."
Rampart currently evaluates the XPath expression against the S:Envelope, so
instead of:
<sp:RequiredElements>
<sp:XPath>wsa:To</sp:XPath>
</sp:RequiredElements>
I must declare:
<sp:RequiredElements>
<sp:XPath>soapenv:Header/wsa:To</sp:XPath>
</sp:RequiredElements>
> Rampart doesn't support RequiredElements Assertion
> --------------------------------------------------
>
> Key: RAMPART-136
> URL: https://issues.apache.org/jira/browse/RAMPART-136
> Project: Rampart
> Issue Type: Bug
> Components: rampart-policy
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
> Fix For: 1.4
>
>
> Rampart doesn't support RequiredElements Assertion defined in the WS -
> Security Policy Specification
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
