Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 06313200C1B for ; Tue, 14 Feb 2017 19:51:40 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 04A5D160B5F; Tue, 14 Feb 2017 18:51:40 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4C4FF160B45 for ; Tue, 14 Feb 2017 19:51:39 +0100 (CET) Received: (qmail 60913 invoked by uid 500); 14 Feb 2017 18:51:38 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 60901 invoked by uid 99); 14 Feb 2017 18:51:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2017 18:51:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 37590C213B for ; Tue, 14 Feb 2017 18:51:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.32 X-Spam-Level: X-Spam-Status: No, score=-0.32 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id BMfnIp1th3kY for ; Tue, 14 Feb 2017 18:51:36 +0000 (UTC) Received: from mail-qt0-f180.google.com (mail-qt0-f180.google.com [209.85.216.180]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id B6A2F5FB44 for ; Tue, 14 Feb 2017 18:51:35 +0000 (UTC) Received: by mail-qt0-f180.google.com with SMTP id x49so118847690qtc.2 for ; Tue, 14 Feb 2017 10:51:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=0m5dbBLDHi5r+s7lvC4R3i4r7NEncbCohPlVihP379s=; b=h4s4a7HTzFqwE7WuGowBgzSinsSrs6VbIul5rTGzJr42zrGRvhNYBJ/UZtC+bX48I4 91jEuQAKbvtUiOD6ZXAsnh42QtHY7v4j+Ol60JmlvMH6efoe3Fvo00PMKNYDlVrXJ3l6 iz7x/EibOcnTSD/lpKO0BP26vP6SrYEHaaaIzPXAKhjpaa5PGzigBQNDfmY3NgBUhlzi 4/A7AOa7dxCu5VaOnumQKF8xyuwH9vpsaiCCrewe694vnANQdbt23klUbfupbBpf8tpc O51x5lo0KiAVceyACBZoKbww3rgLZcUJabVhXD1p5Ftg+hdsX2rfppR1ePPgbh0trqEP aKVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0m5dbBLDHi5r+s7lvC4R3i4r7NEncbCohPlVihP379s=; b=UJrTn9q6iEakM8qLXuY9YsX3z8alk2shsDvtDan9DK2vapENZC7EYbySRwOeOLKxp9 Q2KwbzWzC494sKu+hrPf8Gumace/UNeVft6UJ92KlMDy0CthXiQNxM3NVRLhnza7mP8W jPYf7ObafLLx3aJiMF9WlkVm5MxmbqFuQkQa7JN1btI5/CiPZNCUw6FgMIB+eqQpueMH vhym269HuFUlKYzv8JkNaH62eOnMsAcPeCwf6OZ8W1ANtXnOiSQq0k8lbVmM7lMfHeLS +Ou4tOASFCc0HLiMF1um4F96qo2pLhVcmUOXKTGZx6tnS2PZGsxo79Dsp99t6u8Xfopx T7Hg== X-Gm-Message-State: AMke39nB+Euzmk3CpaiJ1BNmCJI5e4sdAAR5mzfGJfmdWXjdGi9/MPJ/xYjeUbABhdem7R0NgWM6LRBIoCB8Ww== X-Received: by 10.200.49.110 with SMTP id h43mr27332626qtb.249.1487098294612; Tue, 14 Feb 2017 10:51:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.54.81 with HTTP; Tue, 14 Feb 2017 10:51:34 -0800 (PST) In-Reply-To: <1487095528465-7659151.post@n2.nabble.com> References: <1487095528465-7659151.post@n2.nabble.com> From: Robbie Gemmell Date: Tue, 14 Feb 2017 18:51:34 +0000 Message-ID: Subject: Re: [JMS] can I include ssl keystore & truststore in connectionfactory string To: "users@qpid.apache.org" Content-Type: text/plain; charset=UTF-8 archived-at: Tue, 14 Feb 2017 18:51:40 -0000 On 14 February 2017 at 18:05, pqvchen1 wrote: > I'm using qpid-jms-client-0.11.1 and just wonder if there is a way to include > all the keystore & truststore information in connection URL? > > Here is a sample of my connection URL: > Hashtable env = new Hashtable(); > env.put(Context.INITIAL_CONTEXT_FACTORY, > "org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory"); > env.put(Context.PROVIDER_URL, "jndi.properties"); > InitialContext context = new InitialContext(env); > > > connectionfactory.SBCF = amqps://uname:upassword@hostname:port > > Can I add keystore & truststore after port as ?keystore=...& truststore= ??? > > I tried it and it doesn't work. Thanks for helping > > Your InitialContextFactory configuration above is actually for a different older JMS client, please see the following for how to configure things to use qpid-jms-client (also note that the current release is 0.20.0): http://qpid.apache.org/releases/qpid-jms-0.20.0/docs/index.html#configuring-a-jndi-initialcontext To your original question, yes it is possible to configure the details in the URI, see the ssl transport options documentation at: http://qpid.apache.org/releases/qpid-jms-0.20.0/docs/index.html#ssl-transport-configuration-options Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org