You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/30 16:51:00 UTC
[jira] [Commented] (NIFIREG-131) Add logging authentication failure
cases
[ https://issues.apache.org/jira/browse/NIFIREG-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345360#comment-16345360 ]
ASF GitHub Bot commented on NIFIREG-131:
----------------------------------------
GitHub user kevdoran opened a pull request:
https://github.com/apache/nifi-registry/pull/96
NIFIREG-131 Surface auth failure details
Adds logging of root cause for exceptions passed to
AuthenticationEntryPoint.
AuthenticationEntryPoint writes exception message to response body.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevdoran/nifi-registry NIFIREG-131
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/96.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #96
----
commit cd478f5a0cd4a38e4ea67cf115c2a9528bd2bdda
Author: Kevin Doran <kd...@...>
Date: 2018-01-30T16:47:49Z
NIFIREG-131 Surface auth failure details
Adds logging of root cause for exceptions passed to
AuthenticationEntryPoint.
AuthenticationEntryPoint writes exception message to response body.
----
> Add logging authentication failure cases
> ----------------------------------------
>
> Key: NIFIREG-131
> URL: https://issues.apache.org/jira/browse/NIFIREG-131
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Priority: Minor
> Fix For: 0.2.0
>
>
> The handling for unauthenticated requests made to a secured Registry instance swallows authentication exceptions with a vague error message: "AuthenticationEntryPoint invoked as no user identity credentials were found in the request." and an HTTP 401 response is returned with no body to aide in client troubleshooting.
> We should add more useful troubleshooting information (including the root cause) to the logs and some guidance information for the client to the response body.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)