[CMIS-997] MustUnderstand headers:[{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: OpenCMIS 0.12.0
• Labels: patch
• Assignee: Unassigned
• Reporter: santosh kumar das
• Created: 14/Sep/16 14:00
• Updated: 14/Sep/16 14:05
• Resolved: 14/Sep/16 14:05

Description

When trying to use SOAP binding using OpenCMIS and connecting to documentum server we are getting the following exception

com.sun.xml.internal.ws.protocol.soap.MUTube getMisUnderstoodHeaders
INFO: Element not understood=

{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}

Security
Exception: MustUnderstand headers:[{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.

After initial analysis I found that though openCMIS generates the Ws-Security headers for Outbound side, in inbound side it is unable to process Ws-security headers.
Please note that Documentum version 7.1 sends Ws-security headers in the Response.

I have found a workaround where in we can engage SOAP handlers the WSBindingProvider to implicitly instruct JAX-WS to understand the headers,
https://dwuysan.wordpress.com/2012/04/02/jax-ws-wsimport-and-the-error-mustunderstand-headers-not-understood/#comment-215
if we do the changes in PortProvider.java initPortObject() it should resolve the issue. but
In my opinion either OpenCMIS should be modified to provide full support for WS-Security in inbound side.