Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 47934 invoked from network); 21 Jul 2009 05:28:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Jul 2009 05:28:22 -0000 Received: (qmail 76603 invoked by uid 500); 21 Jul 2009 05:29:27 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 76507 invoked by uid 500); 21 Jul 2009 05:29:27 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 76499 invoked by uid 99); 21 Jul 2009 05:29:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jul 2009 05:29:27 +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 asankha.apache@gmail.com designates 209.85.222.174 as permitted sender) Received: from [209.85.222.174] (HELO mail-pz0-f174.google.com) (209.85.222.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jul 2009 05:29:16 +0000 Received: by pzk4 with SMTP id 4so1945725pzk.7 for ; Mon, 20 Jul 2009 22:28:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type; bh=crUsu4e48rpT+a4glUYCJBL7VJjvlSqO77Dp1BKRW6M=; b=xVFgQJFJmWAOSIQjp0bTNNpLPFN8uT3FJG8O85c7o3xdk+qM0HtBSfF45A1WGBwOS1 E8HueL+WoYHQYrfB5S7XhOHkyzyy61/mdR3xC3iUNY32De+mPbOCO4nL323xDg5Isolq HfOxJtxtptE5yGWB61nXHDIaYsI0csYzFQWeU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type; b=w8gy7gi5YYYHoAZMSUQNvuq1kCc5WAye4NedB4fjUskbVOr36kqVyO7DIxlCgkmsqx fp3Qt/BK3Wc8b7Zam1UPen5n74Xs+WTE5dUgA0uIW9Zc99qZUy2p5fKBqrqjeJwojW76 LOdP7pogTvSG3uoMfN/oE81H0k5+3LcjD0TBk= Received: by 10.141.15.6 with SMTP id s6mr2828109rvi.119.1248154134653; Mon, 20 Jul 2009 22:28:54 -0700 (PDT) Received: from ?10.0.0.4? ([124.43.203.241]) by mx.google.com with ESMTPS id l31sm1323991rvb.38.2009.07.20.22.28.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 20 Jul 2009 22:28:53 -0700 (PDT) Sender: Asankha Perera Message-ID: <4A65520F.3030907@apache.org> Date: Tue, 21 Jul 2009 10:58:47 +0530 From: "Asankha C. Perera" User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: dev@synapse.apache.org Subject: Re: Supporting Multiple SSL Configurations at Sender References: <558af1840907200547o1ebdeb43h99f3eb9130b4202c@mail.gmail.com> <558af1840907200702r57fdb811rb5e4c6cf5eeeadf3@mail.gmail.com> <4A647E47.2030706@apache.org> <672a01200907201705k4f058e8bj49e297b6391cbb3e@mail.gmail.com> <4A651CF0.10207@apache.org> <558af1840907202113k424001e9ia67c2d15c764a6d5@mail.gmail.com> In-Reply-To: <558af1840907202113k424001e9ia67c2d15c764a6d5@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: multipart/alternative; boundary="------------030609000907050809090803" X-Virus-Checked: Checked by ClamAV on apache.org --------------030609000907050809090803 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Hiranya > > Can you check "what happens right now" implementing the scenario I > describe with two customers who gives custom client certs to Synapse. > Can you check if 1) that works 2) if it fails - how and where > > > OK I will do some tests with the existing implementation and see where > we can get to. So according to Andreas if we have all the certs in the > provided keystore it should automatically pick the correct one when > talking to different endpoints. Am I correct? Yes.. lets try this.. it will help understand whats happening right now, what needs to be fixed if any, and act as a test/unit test before we code, so that we know that what we expected works correctly when its done cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com --------------030609000907050809090803 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Hiranya
Can you check "what happens right now" implementing the scenario I
describe with two customers who gives custom client certs to Synapse.
Can you check if 1) that works 2) if it fails - how and where

OK I will do some tests with the existing implementation and see where we can get to. So according to Andreas if we have all the certs in the provided keystore it should automatically pick the correct one when talking to different endpoints. Am I correct?

Yes.. lets try this.. it will help understand whats happening right now, what needs to be fixed if any, and act as a test/unit test before we code, so that we know that what we expected works correctly when its done

cheers
asankha
-- 
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com



--------------030609000907050809090803--