In Axis2, the user cannot set inflow and outflow parameters. Therefore, we need to map the Axis2 specific inflow and outflow parameters to WSS4J params (such as action)
action parameters for inflowSecurity are described at http://ws.apache.org/axis2/modules/rampart/1_2/sec-conf/in.action.xsd action parameters for outflowSecurity are described at http://ws.apache.org/axis2/modules/rampart/1_2/sec-conf/out-action.xsd complete examples for inflowSecurity and outflowSecurity are located at Example 1: An outflow configuration to add a timestamp, sign and encrypt the message once policy: http://ws.apache.org/rampart/samples/policy/sample03.xml request: http://ws.apache.org/rampart/samples/msgs/req01.xml response: http://ws.apache.org/rampart/samples/msgs/res01.xml Example 2: An outflow configuration to sign the message twice and add a timestamp policy: http://ws.apache.org/rampart/samples/policy/sample02.xml request: http://ws.apache.org/rampart/samples/msgs/req02.xml response: http://ws.apache.org/rampart/samples/msgs/res02.xml http://ws.apache.org/rampart/samples.html HTH Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Wed, 26 Aug 2009 07:45:08 -0700 > From: sws...@cisco.com > To: axis-dev@ws.apache.org > Subject: Re: Unable to get Header tags in custom module's inflow handler > > > Hi Axis/Rampart Team, > > Could you please provide us any clue why i am facing this issue. Its > very urgent. Please help. > > Thanks, > Swapna Soni. > > soni swapna wrote: > > > > Hi Rampart team, > > > > In a client class we have our custom module and rampart engaged. While > > sending the request, we are setting some header tags in outflow handler of > > custom module. while request going out, first custom module's outflow > > handler is executing then rampart module's outflow handler is executing. > > When request goes til webservice, (webservice is also having rampart and > > custom module engage), then webservice custom module's inflow handler is > > executing. We have a code to extract custom header tags in inflow handler. > > But the custom header tags we have set in outflow handler is not coming > > till inflow handler. And in inflow handler the envelope is in encrypt > > form. Could you please tell me how to get these header values in inflow > > handler. > > > > Please reply as soon as possible. This is very urgent. > > > > Thanks, > > Swapna Soni. > > > > -- > View this message in context: > http://www.nabble.com/Unable-to-get-Header-tags-in-custom-module%27s-inflow-handler-tp25047272p25151399.html > Sent from the Axis - Dev mailing list archive at Nabble.com. > _________________________________________________________________ Windows Live: Keep your friends up to date with what you do online. http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009
