[jira] [Commented] (NIFI-2526) Fix DN order, allow multiple standalone runs, standalone generate client certificates,

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on NIFI-2526:
--------------------------------------

Github user bbende commented on the issue:

    https://github.com/apache/nifi/pull/824
  
    This looks good to me. I am able to build cleanly on a JDK without the unlimited crypto, and I can run the toolkit to generate certs, listing the contents of the client p12 and the keystore/truststore JKS now shows the DN with the CN before the OU.


> Fix DN order, allow multiple standalone runs, standalone generate client certificates, 
> ---------------------------------------------------------------------------------------
>
>                 Key: NIFI-2526
>                 URL: https://issues.apache.org/jira/browse/NIFI-2526
>             Project: Apache NiFi
>          Issue Type: Sub-task
>            Reporter: Bryan Rosander
>            Assignee: Bryan Rosander
>
> NiFi authorization framework currently expects OU to come before CN, the tool should reflect that by default.
> Standalone tool would be much more useful if you could keep running and refining in the same directory with the same CA certificate.
> Standalone tool would be much more useful if it could also generate client certificates.



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