You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Christopher Legan <ch...@lextech.com> on 2012/06/20 23:25:27 UTC
Axis2/Rampart 1.6.2 Policy not supported
I explicitly engage the rampart module on the stub
client.engageModule("rampart-1.6.2");
But I see this issue
------------------
2012-06-20 15:53:29,261 [main] DEBUG org.apache.axis2.description.AxisDescription - can't find any module to process {http://schemas.microsoft.com/xrm/2011/Contracts/Services}AuthenticationPolicy type assertions
2012-06-20 15:53:29,262 [main] DEBUG org.apache.axis2.description.AxisDescription - rahas says it can't support {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}TransportBinding
org.apache.axis2.AxisFault: atleast one module can't support {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}TransportBinding
at org.apache.axis2.description.AxisDescription.engageModulesForPolicy(AxisDescription.java:384)
at org.apache.axis2.description.AxisDescription.applyPolicy(AxisDescription.java:322)
at org.apache.axis2.description.AxisDescription.applyPolicy(AxisDescription.java:327)
-----------------
The policy definition in the client wsdl (which generated the java code) looks like this:
<wsp:Policy wsu:Id="CustomBinding_IDiscoveryService_policy">
<wsp:ExactlyOne>
<wsp:All>
<ms-xrm:AuthenticationPolicy xmlns:ms-xrm="http://schemas.microsoft.com/xrm/2011/Contracts/Services">
<ms-xrm:Authentication>LiveId</ms-xrm:Authentication>
<ms-xrm:SecureTokenService>
<ms-xrm:Identifier>uri:WindowsLiveID</ms-xrm:Identifier>
<ms-xrm:LiveTrust>
<ms-xrm:AppliesTo>urn:crm:dynamics.com</ms-xrm:AppliesTo>
<ms-xrm:TrustVersion>WSTrustFeb2005</ms-xrm:TrustVersion>
<ms-xrm:SecurityMode>TransportWithMessageCredential</ms-xrm:SecurityMode>
<ms-xrm:LivePolicy>MBI_FED_SSL</ms-xrm:LivePolicy>
<ms-xrm:LiveIdAppliesTo>http://Passport.NET/tb</ms-xrm:LiveIdAppliesTo>
</ms-xrm:LiveTrust>
</ms-xrm:SecureTokenService>
</ms-xrm:AuthenticationPolicy>
<sp:TransportBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
... etc ...
------------------
I've reviewed some earlier messages on this, but no explanation was given as to the configuration required (if it is not in fact a bug 1.6.2)
http://mail-archives.apache.org/mod_mbox/axis-java-user/201201.mbox/%3C002d01ccdf6f$91375bf0$b3a613d0$@infoshare-is.com%3E
Any tips? Should I be looking at defining OutflowSecurity in the axis2.xml that feeds the ConfigurationContext? Sorta seems that way but I'm not sure.
Thanks,
Christopher Legan
Sr Software Engineer | Lextech Global Services
christopher.legan@lextech.com
M. 815.630.7635
www.lextech.com | Apps for a Mobile Workforce
Twitter/LextechApps
Re: Axis2/Rampart 1.6.2 Policy not supported
Posted by Kishanthan Thangarajah <ks...@gmail.com>.
On Thu, Jun 21, 2012 at 2:55 AM, Christopher Legan <
christopher.legan@lextech.com> wrote:
> I explicitly engage the rampart module on the stub
>
> client.engageModule("rampart-1.6.2");
>
AFAIK, the above will not engage rampart module. You have to use
"client.engageModule("rampart");" to engage rampart on client side. May be
that is the reason for this issue. Can you try again with the change and
see?
Thanks,
Kishanthan.
>
> But I see this issue
>
> ------------------
>
> 2012-06-20 15:53:29,261 [main] DEBUG
> org.apache.axis2.description.AxisDescription - can't find any module to
> process {http://schemas.microsoft.com/xrm/2011/Contracts/Services}AuthenticationPolicy
> type assertions
> 2012-06-20 15:53:29,262 [main] DEBUG
> org.apache.axis2.description.AxisDescription - rahas says it can't support
> {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702
> }TransportBinding
>
> org.apache.axis2.AxisFault: atleast one module can't support {
> http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}TransportBinding
> at
> org.apache.axis2.description.AxisDescription.engageModulesForPolicy(AxisDescription.java:384)
> at
> org.apache.axis2.description.AxisDescription.applyPolicy(AxisDescription.java:322)
> at
> org.apache.axis2.description.AxisDescription.applyPolicy(AxisDescription.java:327)
>
> -----------------
> The policy definition in the client wsdl (which generated the java code)
> looks like this:
>
> <wsp:Policy wsu:Id="CustomBinding_IDiscoveryService_policy">
> <wsp:ExactlyOne>
> <wsp:All>
> <ms-xrm:AuthenticationPolicy xmlns:ms-xrm="
> http://schemas.microsoft.com/xrm/2011/Contracts/Services">
> <ms-xrm:Authentication>LiveId</ms-xrm:Authentication>
> <ms-xrm:SecureTokenService>
>
> <ms-xrm:Identifier>uri:WindowsLiveID</ms-xrm:Identifier>
> <ms-xrm:LiveTrust>
> <ms-xrm:AppliesTo>urn:crm:dynamics.com
> </ms-xrm:AppliesTo>
>
> <ms-xrm:TrustVersion>WSTrustFeb2005</ms-xrm:TrustVersion>
>
> <ms-xrm:SecurityMode>TransportWithMessageCredential</ms-xrm:SecurityMode>
>
> <ms-xrm:LivePolicy>MBI_FED_SSL</ms-xrm:LivePolicy>
> <ms-xrm:LiveIdAppliesTo>
> http://Passport.NET/tb</ms-xrm:LiveIdAppliesTo>
> </ms-xrm:LiveTrust>
> </ms-xrm:SecureTokenService>
> </ms-xrm:AuthenticationPolicy>
> <sp:TransportBinding xmlns:sp="
> http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
> <wsp:Policy>
> <sp:TransportToken>
> <wsp:Policy>
>
> ... etc ...
> ------------------
>
> I've reviewed some earlier messages on this, but no explanation was given
> as to the configuration required (if it is not in fact a bug 1.6.2)
>
> http://mail-archives.apache.org/mod_mbox/axis-java-user/201201.mbox/%3C002d01ccdf6f$91375bf0$b3a613d0$@infoshare-is.com%3E
>
>
> Any tips? Should I be looking at defining OutflowSecurity in the
> axis2.xml that feeds the ConfigurationContext? Sorta seems that way but
> I'm not sure.
>
> Thanks,
>
> Christopher Legan
> Sr Software Engineer | Lextech Global Services
> christopher.legan@lextech.com <th...@lextech.com>
> M. 815.630.7635
>
> www.lextech.com | Apps for a Mobile Workforce
> Twitter/LextechApps
>
>
>
>