[ 
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)

Reply via email to