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

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

Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/1934
  
    Hi Niels,
    
    Thank you for making a submission to improve NiFi. I totally understand 
your concern that the logs can be busy with these messages when you have a high 
number of users connecting. To even need to deal with this situation means 
you're using NiFi in a productive manner. However, we find that this message in 
particular is extremely helpful in debugging for users who are not as 
successful in configuring and using the application. Being able to identify the 
attempted authentication requests without having to walk them through making 
substantial configuration changes allows faster and more detailed responses. 
    
    However, I definitely empathize with your situation. Can I suggest making a 
local change in your `$NIFI_HOME/conf/logback.xml` file? Two possible solutions 
are changing the log level of the entire package to be `WARN`, as you seem to 
have a good handle on the application and don't need informational alerts on 
successful actions, or elevating the log level for that specific class while 
retaining `INFO` messages for the other actions in that package. 
    
    ## Option 1:
    
    Replace 
    
        <logger name="org.apache.nifi.web.security" level="INFO" 
additivity="false">
            <appender-ref ref="USER_FILE"/>
        </logger>
    
    with
    
        <logger name="org.apache.nifi.web.security" level="WARN" 
additivity="false">
            <appender-ref ref="USER_FILE"/>
        </logger>
    
    
    ## Option 2:
    
    Add
    
        <logger name="org.apache.nifi.web.security.NiFiAuthenticationFilter" 
level="WARN" additivity="false">
            <appender-ref ref="USER_FILE"/>
        </logger>
    
    Either of these two solutions should improve your situation while still 
allowing the community to easily support people who need a bit more help. 
Thanks. 


> NiFiAuthenticationFilter logs "Authentication success" at info level
> --------------------------------------------------------------------
>
>                 Key: NIFI-4106
>                 URL: https://issues.apache.org/jira/browse/NIFI-4106
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Niels Zeilemaker
>
> The NiFiAuthenticationFilter polluting the logs with many "Authentication 
> success" messages. I think those should be changed to debug level to reduce 
> the amount of logging.
> Currently, we have more than one of those lines per second, due to multiple 
> users actively using Nifi, which seems unneccesary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to