Hi Prabath, Thanks for the response. I incorporated the aforementioned changes (i.e modules/rampart-trust-mar/module.xml was already defined this corresponding action, even though /rampart-trust/sts-aar-resources/services.xml wasn't defined the target action).
But the original issue was still reproducing. Earlier as i stated, when debugging the code, we found that the error thrown at the axis2 level (before at the rampart level); where it compares the corresponding action header exist in the sts service wsdl(components/sts/resources/service.wsdl). Since this has not defined in our original sts service wsdl (we cannot duplicate same operation name in wsdl, hence cannot define both of these actions under single wsdl endpoint), it throws this error. This issue can be easily reproducible by requesting a security token with the aforementioned new soap action header. Herewith I have also attached the corresponding error. Thanks, Kasun. On Sun, Mar 6, 2016 at 7:42 PM, Prabath Siriwardana <[email protected]> wrote: > I guess we can do this by updating the > module.xml (modules/rampart-trust-mar/module.xml) and services.xml > (/rampart-trust/sts-aar-resources/services.xml) with the corresponing > action.. > > Thanks & regards, > -Prabath > > On Sat, Mar 5, 2016 at 12:10 AM, Kasun Bandara <[email protected]> wrote: > >> >> Hi all, >> >> I'm in the middle of developing custom components to support WS-Trust >> protocol for Microsoft Dynamics CRM Outlook Connector with Identity server >> 5.1.0. >> >> When analyzing the STS request sent by the Dynamics CRM Outlook Connector >> client, it has been observed that the token request sends a soap action >> header as below; >> >> <a:Action s:mustUnderstand="1"> >> http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue</a:Action> >> >> >> Aforementioned action header isn't supported by the existing STS wsdl >> endpoint, >> instead it supports the following action header; >> >> <a:Action s:mustUnderstand="1"> >> http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue</a:Action> >> >> >> Hence in the Axis2 level, it throws an error stating the action isn't >> recognize and matches with the compatible action headers defined in our >> original STS wsdl. Since we cannot introduce multiple action headers (i.e >> defining both action headers in the existing sts wsdl endpoint) according >> to the WSDL specification, the remaining option is to define a new custom >> STS wsdl endpoint to accommodate the required soap action (i.e >> http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue). >> >> >> Any suggestions and thoughts are highly appreciated. >> >> Thanks & Regards, >> Kasun Bandara. >> >> >> >> >> >> >> >> >> -- >> Kasun Bandara >> *Software Engineer* >> Mobile : +94 (0) 718 338 360 >> <%2B94%20%280%29%20773%20451194> >> [email protected] <[email protected]> >> > > > > -- > Thanks & Regards, > Prabath > > Twitter : @prabath > LinkedIn : http://www.linkedin.com/in/prabathsiriwardena > > Mobile : +1 650 625 7950 > > http://blog.facilelogin.com > http://blog.api-security.org > -- Kasun Bandara *Software Engineer* Mobile : +94 (0) 718 338 360 <%2B94%20%280%29%20773%20451194> [email protected] <[email protected]>
Soap_action_error
Description: Binary data
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
