Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B95D9A33 for ; Sun, 18 Dec 2011 15:16:55 +0000 (UTC) Received: (qmail 34838 invoked by uid 500); 18 Dec 2011 15:16:53 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 34557 invoked by uid 500); 18 Dec 2011 15:16:52 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 34549 invoked by uid 99); 18 Dec 2011 15:16:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Dec 2011 15:16:52 +0000 X-ASF-Spam-Status: No, hits=-2002.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Dec 2011 15:16:51 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id CCA1E11A236 for ; Sun, 18 Dec 2011 15:16:30 +0000 (UTC) Date: Sun, 18 Dec 2011 15:16:30 +0000 (UTC) From: "Ruchith Udayanga Fernando (Resolved) (JIRA)" To: java-dev@axis.apache.org Message-ID: <631813400.24306.1324221390839.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1886667605.10908.1299164622525.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (RAMPART-328) In single service policy if I use two asymmetric binding two apply encryption algorithm for each parameter of a method like multiply multiply(int a, int b) then only single algorithm is applied . MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/RAMPART-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruchith Udayanga Fernando resolved RAMPART-328. ----------------------------------------------- Resolution: Won't Fix Security policy cannot be specific to parts of input of an operation. > In single service policy if I use two asymmetric binding two apply encryption algorithm for each parameter of a method like multiply multiply(int a, int b) then only single algorithm is applied . > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RAMPART-328 > URL: https://issues.apache.org/jira/browse/RAMPART-328 > Project: Rampart > Issue Type: Bug > Components: rampart-core, rampart-policy > Affects Versions: 1.5.1 > Environment: Windows XP service pack2, Axis2 1.5.4, Rampart 1.5.1, jdk 1.5_06, Apache Tomcat 5.5.17 > Reporter: Abhinav Mishra > Labels: security > Attachments: Client.java, Multiplication9.aar, Multiplication9.java, PWCBHandler.java, RequestResponseLog.txt, client.jks, policy.xml, service.jks, services.xml > > Original Estimate: 672h > Remaining Estimate: 672h > > I want to encrypt each parameter of a method of a service by different algorithm. > Like, > if method is: > multiplication(int a,int b) > then > parameter a by TripleDES > parameter b by AES256 > for this I defined two asymmetric binding assertions in my services.xml and policy.xml defining algorithmsuite as Basic256 and TripleDesRas15 in those two asymmetric binding assertions respectively. > > But when i run my client only one algorithm is applied over both the parameters for eg. only aes 256 is applied for both a and b which I don,t want. > So, can anybody suggest me a solution for this problem so that I can encrypt each parameter by using different algorithm. > Here I am attaching my Client Code(client.java ), Service code(Multiplication9.java) and server side policy(services.xml) and client side policy (policy.xml), keystore for client and service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org