[
https://issues.apache.org/jira/browse/NIFI-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399980#comment-15399980
]
ASF GitHub Bot commented on NIFI-2339:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/726
@joewitt I'm still seeing a bunch of details in error messages coming back
to the client. Specifically what I'm seeing right now, it looks like
StandardProcessGroup is using the toString of it's encapsulated components when
generating exception message. We should ensure these toString's don't include
those details.
You should be able to see examples of some of these by issuing requests
that are invalid. Like deleting a component that has an incoming connection,
deleting a group in an invalid state (when data is enqueued in an encapsulated
connection), etc.
> Component details need to be removed from all error messages
> ------------------------------------------------------------
>
> Key: NIFI-2339
> URL: https://issues.apache.org/jira/browse/NIFI-2339
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Joseph Witt
> Priority: Blocker
> Fix For: 1.0.0
>
>
> Error and informative message often contain component details which need to
> be scrubbed when the user is not authorized for reading that component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
