axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepu Janardhanan (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RAMPART-333) Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security
Date Tue, 14 Jun 2011 11:17:47 GMT

     [ https://issues.apache.org/jira/browse/RAMPART-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Deepu Janardhanan resolved RAMPART-333.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.1

It shoudl be noted that this issue is not solved in the version 1.4.1
Some clustering error was showing
On using axis2 1.5.1 and rampart 1.5.1, we are able to resolve the issue

> Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
: Security
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-333
>                 URL: https://issues.apache.org/jira/browse/RAMPART-333
>             Project: Rampart
>          Issue Type: Question
>          Components: rampart-core
>    Affects Versions: 1.5.1
>         Environment: Windows Xp
>            Reporter: Deepu Janardhanan
>              Labels: security
>             Fix For: 1.5.1
>
>         Attachments: axis2.xml, module.xml, policy.xml
>
>
> On receiving the fault response with security header, axis2(version 1.5.1)  is showing
the error "Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
: Security"
> I have added SecurityInHandler in the <InFaultFlow> tag in module.xml in the rampart.mar
file (rampart version is 1.5.1)
> The <InFaultFlow> tag in the module.xml will looks like this
>     <InFaultFlow>
>         <handler name="PolicyBasedSecurityInHandler" class="org.apache.rampart.handler.RampartReceiver">
>             <order phase="Security" phaseFirst="true"/>
>         </handler>
>         <handler name="SecurityInHandler" class="org.apache.rampart.handler.WSDoAllReceiver">
>             <order phase="Security"/>
>         </handler>
>         <handler name="PostDispatchVerificationHandler" class="org.apache.rampart.handler.PostDispatchVerificationHandler">
>             <order phase="Dispatch" phaseLast="true"/>
>         </handler>
>     </InFaultFlow>
> But still this error in security is coming.
> On checking the WSDoAllReceiver.java file in rampart-src-1.5.1\modules\rampart-core\src\main\java\org\apache\rampart\handler
> It is found that in the method processBasic(...){
> ...........
> .....
> // Do not process faults
>         SOAPConstants soapConstants = WSSecurityUtil.getSOAPConstants(doc
>                 .getDocumentElement());
>         if (WSSecurityUtil.findElement(doc.getDocumentElement(), "Fault",
>                 soapConstants.getEnvelopeURI()) != null) {
>             return;
>         }
> ...........
> ...........
> }
> It is not processing if fault is seen.
> Is this a bug?
> If no, how do i read the fault response with security header?
> Please tell how to resolve this issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message