Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 5593 invoked from network); 26 Aug 2009 20:24:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Aug 2009 20:24:30 -0000 Received: (qmail 54941 invoked by uid 500); 26 Aug 2009 20:24:29 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 54831 invoked by uid 500); 26 Aug 2009 20:24:29 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 54822 invoked by uid 99); 26 Aug 2009 20:24:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2009 20:24:29 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mgainty@hotmail.com designates 65.55.116.91 as permitted sender) Received: from [65.55.116.91] (HELO blu0-omc3-s16.blu0.hotmail.com) (65.55.116.91) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2009 20:24:16 +0000 Received: from BLU142-W4 ([65.55.116.72]) by blu0-omc3-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 26 Aug 2009 13:23:55 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_64059e16-6d28-46ef-a034-b0d5f7f270d5_" X-Originating-IP: [72.93.158.184] From: Martin Gainty To: Subject: RE: Unable to get Header tags in custom module's inflow handler Date: Wed, 26 Aug 2009 16:23:55 -0400 Importance: Normal In-Reply-To: <25151399.post@talk.nabble.com> References: <25047272.post@talk.nabble.com> <25151399.post@talk.nabble.com> MIME-Version: 1.0 X-OriginalArrivalTime: 26 Aug 2009 20:23:55.0517 (UTC) FILETIME=[2288A2D0:01CA268B] X-Virus-Checked: Checked by ClamAV on apache.org --_64059e16-6d28-46ef-a034-b0d5f7f270d5_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In Axis2=2C the user cannot set inflow and outflow parameters. Therefore=2C we need to map the Axis2 specific inflow and outflow parameters to WSS4J=20 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=2C 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 tim= estamp 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=20 ______________________________________________=20 Verzicht und Vertraulichkeitanmerkung/Note de d=E9ni et de confidentialit= =E9 =20 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaeng= er sein=2C so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiter= leitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient l= ediglich dem Austausch von Informationen und entfaltet keine rechtliche Bin= dungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen w= ir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut =EAtre privil=E9gi=E9. Si vous n'=EAtes= pas le destinataire pr=E9vu=2C nous te demandons avec bont=E9 que pour sat= isfaire informez l'exp=E9diteur. N'importe quelle diffusion non autoris=E9e= ou la copie de ceci est interdite. Ce message sert =E0 l'information seule= ment et n'aura pas n'importe quel effet l=E9galement obligatoire. =C9tant d= onn=E9 que les email peuvent facilement =EAtre sujets =E0 la manipulation= =2C nous ne pouvons accepter aucune responsabilit=E9 pour le contenu fourni= . > Date: Wed=2C 26 Aug 2009 07:45:08 -0700 > From: swsoni@cisco.com > To: axis-dev@ws.apache.org > Subject: Re: Unable to get Header tags in custom module's inflow handler >=20 >=20 > Hi Axis/Rampart Team=2C >=20 > Could you please provide us any clue why i am facing this issue. It= s > very urgent. Please help. >=20 > Thanks=2C > Swapna Soni. >=20 > soni swapna wrote: > >=20 > > Hi Rampart team=2C > >=20 > > In a client class we have our custom module and rampart engaged. Wh= ile > > sending the request=2C we are setting some header tags in outflow handl= er of > > custom module. while request going out=2C first custom module's outflow > > handler is executing then rampart module's outflow handler is executing= . > > When request goes til webservice=2C (webservice is also having rampart = and > > custom module engage)=2C then webservice custom module's inflow handler= is > > executing. We have a code to extract custom header tags in inflow handl= er. > > 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.=20 > >=20 > > Please reply as soon as possible. This is very urgent. > >=20 > > Thanks=2C > > Swapna Soni. > >=20 >=20 > --=20 > 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. >=20 _________________________________________________________________ Windows Live: Keep your friends up to date with what you do online. http://windowslive.com/Campaign/SocialNetworking?ocid=3DPID23285::T:WLMTAGL= :ON:WL:en-US:SI_SB_online:082009= --_64059e16-6d28-46ef-a034-b0d5f7f270d5_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In Axis2=2C the user cannot set inflow and outflow parameters.
Therefore=2C we need to map the Axis2 specific inflow and outflow parameters to WSS4J
params (such as action)

action parameters f= or inflowSecurity are described at
http://ws.apache.org/axis2/modules/ra= mpart/1_2/sec-conf/in.action.xsd

action parameters for outflo= wSecurity are described at
http://ws.apache.org/axis2/modules/rampart/1_= 2/sec-conf/out-action.xsd

complete examples for inflowSecurity and o= utflowSecurity are located at

Example 1: An outflow configuration to= add a timestamp=2C sign and encrypt the message once

policy: = =3B =3B =3B =3B =3B http://ws.apache.org/rampart/samples/po= licy/sample03.xml
request: =3B 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 a= nd add a timestamp

policy: =3B =3B =3B =3B =3B&n= bsp=3B http://ws.apache.org/rampart/samples/policy/sample02.xml
request:=  =3B =3B =3B http://ws.apache.org/rampart/samples/msgs/req02.xm= l
response: http://ws.apache.org/rampart/samples/msgs/res02.xml

h= ttp://ws.apache.org/rampart/samples.html
HTH
Martin Gainty
______= ________________________________________
Verzicht und Vertraulichkeitan= merkung/Note de d=E9ni et de confidentialit=E9
 =3B
Diese Na= chricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein= =2C so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung= oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglic= h dem Austausch von Informationen und entfaltet keine rechtliche Bindungswi= rkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir kein= e Haftung fuer den Inhalt uebernehmen.
Ce message est confide=
ntiel et peut =EAtre privil=E9gi=E9. Si vous n'=EAtes pas le destinataire p=
r=E9vu=2C nous te demandons avec bont=E9 que pour satisfaire informez l'exp=
=E9diteur. N'importe quelle diffusion non autoris=E9e ou la copie de ceci e=
st interdite. Ce message sert =E0 l'information seulement et n'aura pas n'i=
mporte quel effet l=E9galement obligatoire. =C9tant donn=E9 que les email p=
euvent facilement =EAtre sujets =E0 la manipulation=2C nous ne pouvons acce=
pter aucune responsabilit=E9 pour le contenu fourni.




<= br>>=3B Date: Wed=2C 26 Aug 2009 07:45:08 -0700
>=3B From: swsoni@ci= sco.com
>=3B To: axis-dev@ws.apache.org
>=3B Subject: Re: Unable = to get Header tags in custom module's inflow handler
>=3B
>=3B <= br>>=3B Hi Axis/Rampart Team=2C
>=3B
>=3B Could you plea= se provide us any clue why i am facing this issue. Its
>=3B very urgen= t. Please help.
>=3B
>=3B Thanks=2C
>=3B Swapna Soni.
&g= t=3B
>=3B soni swapna wrote:
>=3B >=3B
>=3B >=3B Hi Ra= mpart team=2C
>=3B >=3B
>=3B >=3B In a client class we h= ave our custom module and rampart engaged. While
>=3B >=3B sending t= he request=2C we are setting some header tags in outflow handler of
>= =3B >=3B custom module. while request going out=2C first custom module's = outflow
>=3B >=3B handler is executing then rampart module's outflow= handler is executing.
>=3B >=3B When request goes til webservice=2C= (webservice is also having rampart and
>=3B >=3B custom module enga= ge)=2C then webservice custom module's inflow handler is
>=3B >=3B e= xecuting. We have a code to extract custom header tags in inflow handler.>=3B >=3B But the custom header tags we have set in outflow handler i= s not coming
>=3B >=3B till inflow handler. And in inflow handler th= e envelope is in encrypt
>=3B >=3B form. Could you please tell me ho= w to get these header values in inflow
>=3B >=3B handler.
>=3B= >=3B
>=3B >=3B Please reply as soon as possible. This is ver= y urgent.
>=3B >=3B
>=3B >=3B Thanks=2C
>=3B >=3B Swa= pna Soni.
>=3B >=3B
>=3B
>=3B --
>=3B View this me= ssage in context: http://www.nabble.com/Unable-to-get-Header-tags-in-custom= -module%27s-inflow-handler-tp25047272p25151399.html
>=3B Sent from the= Axis - Dev mailing list archive at Nabble.com.
>=3B

W= indows Live: Keep your friends up to date with what you do online. Find out more. = --_64059e16-6d28-46ef-a034-b0d5f7f270d5_--