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 93643200C1B for ; Tue, 14 Feb 2017 21:44:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 91D90160B5F; Tue, 14 Feb 2017 20:44:52 +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 DCF2C160B45 for ; Tue, 14 Feb 2017 21:44:51 +0100 (CET) Received: (qmail 28796 invoked by uid 500); 14 Feb 2017 20:44:46 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 28787 invoked by uid 99); 14 Feb 2017 20:44:46 -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 20:44:46 +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 82B8DC2154 for ; Tue, 14 Feb 2017 20:44:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.198 X-Spam-Level: X-Spam-Status: No, score=-1.198 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ooX530Qbomrr for ; Tue, 14 Feb 2017 20:44:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8312C60F56 for ; Tue, 14 Feb 2017 20:44: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 B1C01E07E4 for ; Tue, 14 Feb 2017 20:44:42 +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 E7FE324142 for ; Tue, 14 Feb 2017 20:44:41 +0000 (UTC) Date: Tue, 14 Feb 2017 20:44:41 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-3331) TLS Toolkit - add the possibility to define a SAN in issued certificates MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 14 Feb 2017 20:44:52 -0000 [ https://issues.apache.org/jira/browse/NIFI-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866629#comment-15866629 ] ASF GitHub Bot commented on NIFI-3331: -------------------------------------- Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/1491#discussion_r101138547 --- Diff: nifi-toolkit/nifi-toolkit-tls/src/test/java/org/apache/nifi/toolkit/tls/service/client/TlsCertificateSigningRequestPerformerTest.java --- @@ -106,7 +106,7 @@ public void setup() throws GeneralSecurityException, OperatorCreationException, when(tlsClientConfig.getPort()).thenReturn(testPort); when(tlsClientConfig.createCertificateSigningRequestPerformer()).thenReturn(tlsCertificateSigningRequestPerformer); when(tlsClientConfig.getSigningAlgorithm()).thenReturn(TlsConfig.DEFAULT_SIGNING_ALGORITHM); - JcaPKCS10CertificationRequest jcaPKCS10CertificationRequest = TlsHelper.generateCertificationRequest(tlsClientConfig.getDn(), keyPair, TlsConfig.DEFAULT_SIGNING_ALGORITHM); + JcaPKCS10CertificationRequest jcaPKCS10CertificationRequest = TlsHelper.generateCertificationRequest(tlsClientConfig.getDn(), null, keyPair, TlsConfig.DEFAULT_SIGNING_ALGORITHM); --- End diff -- There should be new tests to cover the added functionality. > TLS Toolkit - add the possibility to define a SAN in issued certificates > ------------------------------------------------------------------------ > > Key: NIFI-3331 > URL: https://issues.apache.org/jira/browse/NIFI-3331 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build > Reporter: Pierre Villard > Assignee: Pierre Villard > Labels: tls-toolkit > Fix For: 1.2.0 > > > To ease the deployment of a load balancer in front of NiFi, it would be nice to allow users to define a SAN in certificates issued by the CA. > To load balance the access to the UI or even with a ListenHTTP processor, both will cause errors with a "Host mismatch" kind of error because of different fqdn between nodes certificate and LB certificate. This is also discussed here: http://stackoverflow.com/questions/40035356/nifi-load-balancer -- This message was sent by Atlassian JIRA (v6.3.15#6346)