Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 85157 invoked from network); 6 Apr 2006 10:11:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Apr 2006 10:11:50 -0000 Received: (qmail 70916 invoked by uid 500); 6 Apr 2006 10:11:04 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 70889 invoked by uid 500); 6 Apr 2006 10:11:03 -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 70878 invoked by uid 99); 6 Apr 2006 10:11:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2006 03:11:03 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of xjchen001@gmail.com designates 64.233.182.185 as permitted sender) Received: from [64.233.182.185] (HELO nproxy.gmail.com) (64.233.182.185) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2006 03:11:02 -0700 Received: by nproxy.gmail.com with SMTP id n15so73398nfc for ; Thu, 06 Apr 2006 03:10:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Aq8fYgctRdnq7apFJkV6NB9XUME9Vbii9mK8OGrh9kxCPHV86k8WZdVp6IaJdC0r9yyu+Rk7kNglAIOADiLkf5KUKeyes33fqg7S4c8/dU1vsBzJg8Wm0RHkMaMp7DLlY/NK8jTqZxWxRhxlUidqgdrVVgoGUPEUBr8QtEPnZ1Y= Received: by 10.48.48.20 with SMTP id v20mr480485nfv; Thu, 06 Apr 2006 03:10:41 -0700 (PDT) Received: by 10.48.226.12 with HTTP; Thu, 6 Apr 2006 03:10:41 -0700 (PDT) Message-ID: <84f31d220604060310i1a37253fm7cd9f4a66bdae869@mail.gmail.com> Date: Thu, 6 Apr 2006 18:10:41 +0800 From: "Xinjun Chen" To: axis-user@ws.apache.org Subject: [Axis2] Client side configuration parameters MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N When testing the Axis2 0.94 security module, I have some questions regarding client side configuration. I raised the following question after reading the webpage http://ws.apache.org/axis2/0_94/security-module.html. 1. The page mentions that client side configuration parameters can be set in the axis2.xml of the client's Axis2 repository. My question is is this referring to the directory \axis2-std-0.94-bin\repository\services ? It is initially empty. What will be the root element in the client respository axis2.xml? Could you help me to get some sample client side configuration? 2. If a developer only downloaded WAR distribution and put the war inside the Tomcat webapps folder. Can he/she still configure the client side? How? 3. The page mentioned per service level security configuration. Could you also provided some details? My understanding is that the security configuration (security policy and security information) will be read by the WSDoAllHandler inside the security.module. I checked both WSDoAllSender and WSDoAllReceiver, but could not figure out where how can WSDoAllHandler find out the security configuration file. 4. As for the PasswordCallbackClass, is it possible to use the same PasswordCallbackClass for both client and server if I combine the client and server into the Axis2 installation in Tomcat? 5. Does Axis2 security module allow plain username and password for authentication? Can I specify the username and password inside the configuration? Regards, Xinjun