[RAMPART-169] HttpsToken serializer does not support ws-securitypolicy 1.2

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3
• Fix Version/s: 1.4
• Component/s: rampart-policy
• Environment: any
• Assignee: Nandana Mihindukulasooriya
• Reporter: Stefan Vladov
• Created: 22/May/08 15:52
• Updated: 23/Jun/08 12:58
• Resolved: 23/Jun/08 12:58

Description

org.apache.ws.secpolicy.model.HttpsToken will always serialize the RequireClientCertificate as specified in ws-securitypolicy, i.e. as an attribute on the HttpsToken element. However as of ws-securitypolicy 1.2 it should be specified as:

<sp:HttpsToken>
<wsp:Policy>
<sp:RequireClientCertificate/>
</wsp:Policy>
</sp:HttpsToken>

Notably the token builder for the ws-securitypolicy 1.2 works correctly and deserializes the token as specified in version 1.2 of the spec.

Additionally, since rampart claims ws-securitypolicy 1.2 support shouldn't it also consider the other two available elements for the HttpsToken, namely:
<sp:HttpBasicAuthentication />
<sp:HttpDigestAuthentication />

Although these are not handled by rampart, they could be used for policy validation.

Should I supply a diff?