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 7F37C200C41 for ; Fri, 24 Mar 2017 17:55:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7DF1A160B9A; Fri, 24 Mar 2017 16:55:49 +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 CD02E160B93 for ; Fri, 24 Mar 2017 17:55:48 +0100 (CET) Received: (qmail 96126 invoked by uid 500); 24 Mar 2017 16:55:46 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 95739 invoked by uid 99); 24 Mar 2017 16:55:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Mar 2017 16:55:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 27BD318612B for ; Fri, 24 Mar 2017 16:55:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id zkO4LMx2QUMM for ; Fri, 24 Mar 2017 16:55:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id DA2E95FB86 for ; Fri, 24 Mar 2017 16:55:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0195CE0D20 for ; Fri, 24 Mar 2017 16:55:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1ADE42407B for ; Fri, 24 Mar 2017 16:55:42 +0000 (UTC) Date: Fri, 24 Mar 2017 16:55:42 +0000 (UTC) From: "Colm O hEigeartaigh (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CXF-7299) No way to configure TLS for the JettyHTTPServerEngineFactory in code MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 24 Mar 2017 16:55:49 -0000 Colm O hEigeartaigh created CXF-7299: ---------------------------------------- Summary: No way to configure TLS for the JettyHTTPServerEngineFactory in code Key: CXF-7299 URL: https://issues.apache.org/jira/browse/CXF-7299 Project: CXF Issue Type: Bug Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.2.0, 3.1.11 Currently there is no way to configure TLS for the JettyHTTPServerEngineFactory in code. "createJettyHTTPServerEngine" passes "null" through to "getOrCreate" for the TLSServerParameters object and an exception will then be thrown when comparing the protocol of the engine to "https". The fix is to add an argument which indexes in to the tlsParametersMap. If found then this will be used to configure TLS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)