Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 67992 invoked from network); 11 Aug 2008 14:09:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Aug 2008 14:09:38 -0000 Received: (qmail 94614 invoked by uid 500); 11 Aug 2008 14:09:29 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 94587 invoked by uid 500); 11 Aug 2008 14:09:29 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 94576 invoked by uid 99); 11 Aug 2008 14:09:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Aug 2008 07:09:29 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nandana.cse@gmail.com designates 209.85.142.190 as permitted sender) Received: from [209.85.142.190] (HELO ti-out-0910.google.com) (209.85.142.190) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Aug 2008 14:08:31 +0000 Received: by ti-out-0910.google.com with SMTP id y6so1300213tia.18 for ; Mon, 11 Aug 2008 07:08:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=7hNrAaJD+lCFLqgMGNHsXcLxBK/f/tFwrDVrquITUIw=; b=wgJeptNmq2qbQJUG7OOfwW2OqnuNeUz3VWiCQzPr9Db0AzUOenv6FIRoh7M365WmDO 6puMeiR0UJDLWFr5Phw3kMoYbv097YL08XkmKRr/CbWaD9xxGp3PvVwGUIppqtD88uv/ hKXRYIqMWwuej8lx3brq6ZGLkpjiE14ecSryE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=qkQxTyphNhdre3b66GTSA+0+c6mejxGaTTuBXxqY8L74XOtH8djunTKYz+ZvM2w1ng o68T1xejFoMzMapZAfcjiaHlj/QUnC9T47qXUgTYF2W38edMR4yPxLaHUq7OxfFf0oVr Hcwidqi2BTgXR00MhJq44srRC4ECoUNIY6t0U= Received: by 10.110.53.14 with SMTP id b14mr9587616tia.8.1218463737691; Mon, 11 Aug 2008 07:08:57 -0700 (PDT) Received: by 10.110.20.20 with HTTP; Mon, 11 Aug 2008 07:08:57 -0700 (PDT) Message-ID: <9e2fff830808110708t1ee6af58j2a7854d4315d256a@mail.gmail.com> Date: Mon, 11 Aug 2008 19:38:57 +0530 From: "Nandana Mihindukulasooriya" To: axis-user@ws.apache.org Subject: Re: Axis2 1.4 - Rampart 1.4 - Policy not applied - Axis WebService using Axis Stub for calling thirdparty webservice In-Reply-To: <18926027.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_69416_3126766.1218463737697" References: <18923303.post@talk.nabble.com> <9e2fff830808110536g6743b63bj887ffdd83c5b21eb@mail.gmail.com> <18926027.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_69416_3126766.1218463737697 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Greg, You need to have the policy in a separate file and refer to is with in the services.xml ? Nope, at the moment, you cannot have such external policy references in the services.xml. Policy need to be embedded in to services.xml. thanks, nandana Now, I need to activate rampart for my webservice (request must be signed). > Is it possible to reference (using a full path, ...) a policy file from > within the service.xml ? > > Thanks > Greg > > > > > Nunny wrote: > > > > Hi Gr=E9gory, > > > > 2/ I write a webservice that will receive request and use the previous > >> generated stub to call the thirdparty webservice. At this stage Rampa= rt > >> is > >> not engaged for the webservice. > > > > > > Sory, I didn't get a clear idea about the scenario. Can you please > explain > > this second scenario in bit more detail. It seems that at the point of > > building the policy, rampart-policy / rampart-core jars are not availab= le > > in > > the class path. As we can see from your debug dumps, in the second > > scenario > > the assertions are built as XMLPrimitiveAssertion instances and not as > > SecurityPolicyAssertion instances. How is assertion building is done is > > described in this [1] blog post. Please explain this second scenario in > > detail and we will be able to figure out what's going wrong. > > > > > > thanks, > > nandana > > > > [1] - > > > http://nandana83.blogspot.com/2008/07/why-cant-we-ship-as-standalone-modu= le.html > > > > -- > > Nandana Mihindukulasooriya > > WSO2 inc. > > > > http://nandana83.blogspot.com/ > > http://www.wso2.org > > > > > > -- > View this message in context: > http://www.nabble.com/Axis2-1.4---Rampart-1.4---Policy-not-applied---Axis= -WebService-using-Axis-Stub-for-calling-thirdparty-webservice-tp18923303p18= 926027.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > --=20 Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org ------=_Part_69416_3126766.1218463737697 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Greg,
        You= need to have the policy in a separate file and refer to is with in the ser= vices.xml ? Nope, at the moment, you cannot have such external policy refer= ences in the services.xml. Policy need to be embedded in to services.xml.&n= bsp;

thanks,
nandana

Now, I need to activate rampart fo= r my webservice (request must be signed).
Is it possible to reference (using a full path, ...) a policy file from
within the service.xml ?

Thanks
Greg




Nunny wrote:
>
>  Hi Gr=E9gory,
>
> 2/ I write a webservice that will receive request and use the previous=
>> generated stub to call the thirdparty webservice.  At this st= age Rampart
>> is
>> not engaged for the webservice.
>
>
> Sory, I didn't get a clear idea about the scenario. Can you please= explain
> this second scenario in bit more detail. It seems that at the point of=
> building the policy, rampart-policy / rampart-core jars are not availa= ble
> in
> the class path. As we can see from your debug dumps, in the second
> scenario
> the assertions are built as XMLPrimitiveAssertion instances and not as=
> SecurityPolicyAssertion instances. How is assertion building is done i= s
> described in this [1] blog post. Please explain this second scenario i= n
> detail and we will be able to figure out what's going wrong.
>
>
> thanks,
> nandana
>
> [1] -
> http://nandana83.blogspot.com/2008= /07/why-cant-we-ship-as-standalone-module.html
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://na= ndana83.blogspot.com/
> http://www.wso2.org<= /a>
>
>

--
View this message in context: http:= //www.nabble.com/Axis2-1.4---Rampart-1.4---Policy-not-applied---Axis-WebSer= vice-using-Axis-Stub-for-calling-thirdparty-webservice-tp18923303p18926027.= html
Sent from the Axis - User mail= ing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org




--
Nandana Mih= indukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
= http://www.wso2.org
------=_Part_69416_3126766.1218463737697--