[ 
https://issues.apache.org/jira/browse/NIFI-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364872#comment-15364872
 ] 

ASF subversion and git services commented on NIFI-2119:
-------------------------------------------------------

Commit bd69f81af5d03d1455b48169725f57caf8d4e883 in nifi's branch refs/heads/0.x 
from [~alopresto]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bd69f81 ]

NIFI-2119 Refactored CertificateUtils to separate logic for DN extraction from 
server/client sockets. Added logic to detect server/client mode encapsulated in 
exposed method.
Added unit tests for DN extraction.
Corrected typo in Javadoc.
Switched server/client socket logic for certificate extraction -- when the 
local socket is in client/server mode, the peer is necessarily the inverse.
Fixed unit tests.
Moved lazy-loading authentication access out of isDebugEnabled() control branch.
This closes #611


> Secure clustering returning bad request response
> ------------------------------------------------
>
>                 Key: NIFI-2119
>                 URL: https://issues.apache.org/jira/browse/NIFI-2119
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Joseph Witt
>             Fix For: 0.7.0
>
>
> Cannot get a secured cluster working that worked well on 0.6.0.  After 
> upgrading now seeing the following line.  It either means I upgraded 
> incorrectly, or we're missing critical migration guidance, or we have 
> introduced a new bug.
>   2016-06-25 14:19:12,017 INFO [NiFi Web Server-23] 
> o.a.n.w.a.c.IllegalArgumentExceptionMapper 
> java.lang.IllegalArgumentException: User account already created 
> CN=box1.testing.org, OU=NIFI, O=Apache-NiFi, L=Here, ST=There, C=EVERYWHERE. 
> Returning Bad Request response.
> Speaking with [~mcgilman] about this he looked into it and says
> "the socket used for cluster communications is configured with an sslContext 
> that has client auth set to none... which seems to be why the we're not 
> getting the NCM DN during connection
> i think the issue is this part of this commit.... 
> https://github.com/apache/nifi/commit/7b5583f3a8c8e3f62e2985059a3466a5bb36f4e8#diff-a14f46a45c394fbd82a2b99730e04bcbR68";



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to