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

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

Github user jvwing commented on the pull request:

    https://github.com/apache/nifi/pull/267#issuecomment-216644453
  
    I added a new CLI utility that just hashes passwords using Bcrypt.  For the 
moment, I left the rest of the code alone.  I'm still struggling with how to 
best package and distribute any command-line utility.  There are currently a 
couple of undesirable steps to running this: 
    
    1. Build a standalone jar of nifi-file-identity-provider using `mvn compile 
assembly:single`
    1. Run the standalone jar like `java -jar 
nifi-file-identity-provider-1.0.0-SNAPSHOT-jar-with-dependencies.jar`
    
    I do not know how to run the class from within the NAR file.  It seems like 
we would need to get the module to compile to JAR, get the JAR in the lib 
folder, and then make a shell script to wrap the nice java syntax.  Any ideas 
on that?


> Simple Username/Password Authentication
> ---------------------------------------
>
>                 Key: NIFI-1614
>                 URL: https://issues.apache.org/jira/browse/NIFI-1614
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: James Wing
>            Priority: Minor
>
> NiFi should include a simple option for username/password authentication 
> backed by a local file store.  NiFi's existing certificate and LDAP 
> authentication schemes are very secure.  However, the configuration and setup 
> is complex, making them more suitable for long-lived corporate and government 
> installations, but less accessible for casual or short-term use.  Simple 
> username/password authentication would help more users secure more NiFi 
> installations beyond anonymous admin access.



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

Reply via email to