[ 
https://issues.apache.org/jira/browse/RAMPART-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416966#comment-13416966
 ] 

Yoann Guerro commented on RAMPART-371:
--------------------------------------

I had the same issue and solved it by removing Rahas mar file from the axis2 
modules repositories.

After digging into the code, the problem comes from the Rahas class in the 
rampart-trust module which has been introduced with Rampart 1.6.2.
The method "boolean canSupportAssertion(Assertion assertion)" returns always 
false.
A debug log message shows:

        rahas says it can't support 
{http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens

Removing the Rahas module from Axi2 module repository solves the issue.

However, if Rahas is needed for WS-Trust support, the workaround is not usable. 
The issue is therefore still valid.
                
> Namespace 'http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702' is 
> unsupported by generated client
> --------------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-371
>                 URL: https://issues.apache.org/jira/browse/RAMPART-371
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-policy
>    Affects Versions: 1.6.2
>            Reporter: Philippe A
>            Priority: Minor
>
> According to the documentation [1], Rampart supports WS Security Policy 1.2 
> [2]. I assumed the corresponding namespace would be supported:
>     The XML namespace URI that MUST be used by implementations of this 
> specification is:
>     http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702
> However, this namespace is at the origin of an exception in my generated 
> client:
> org.apache.axis2.AxisFault: atleast one module can't support 
> {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens
> One workaround is to 'downgrade' the namespace to WS Security Policy 1.1 [3] 
> in my server policy, and to regenerate my client:
>     http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
> I have not encountered that problem with a simple hand written client.
> [1] http://axis.apache.org/axis2/java/rampart/
> [2] 
> http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.html
> [3] http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to