[jira] [Updated] (NIFI-8194) Extraneous WARN log messages about authentication protocols not being configured

["Jon Kessler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Kessler updated NIFI-8194:
------------------------------
    Status: Patch Available  (was: In Progress)

> Extraneous WARN log messages about authentication protocols not being configured
> --------------------------------------------------------------------------------
>
>                 Key: NIFI-8194
>                 URL: https://issues.apache.org/jira/browse/NIFI-8194
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.13.0
>            Reporter: Mark Payne
>            Assignee: Jon Kessler
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When running a secure instance (secured via TLS), each time that a user opens a browser to a NiFi instance, the following logs are dumped into `nifi-app.log`:
> {code:java}
> 2021-02-03 11:35:57,559 WARN [NiFi Web Server-25] org.apache.nifi.web.api.AccessResource Kerberos ticket login not supported by this NiFi.
> 2021-02-03 11:35:57,616 WARN [NiFi Web Server-22] org.apache.nifi.web.api.AccessResource OpenId Connect support is not configured
> 2021-02-03 11:35:57,624 WARN [NiFi Web Server-25] org.apache.nifi.web.api.AccessResource SAML support is not configured {code}
> These should probably go into the nifi-user.log instead of nifi-app.log. But more importantly, the fact that they are not configured is very normal and not worthy of a warning. It should be INFO level at max, probably DEBUG level.
> It's unclear if these warnings were appearing before 1.13, but I think they were in the user log instead of the app log. Could be mistaken about that, though.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)