[
https://issues.apache.org/jira/browse/NIFI-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398561#comment-15398561
]
ASF GitHub Bot commented on NIFI-1876:
--------------------------------------
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/694#discussion_r72731831
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/EntityFactory.java
---
@@ -77,6 +77,8 @@ public ProcessorEntity createProcessorEntity(final
ProcessorDTO dto, final Revis
if (dto != null) {
entity.setPermissions(permissions);
entity.setStatus(status);
+ status.setCanRead(permissions.getCanRead());
--- End diff --
Yup, hit it when I was trying to delete a connection:
2016-07-28 21:41:44,415 INFO [NiFi Web Server-231]
org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous)
DELETE
http://localhost:8080/nifi-api/connections/344c598c-0156-1000-0000-000053115355
(source ip: 127.0.0.1)
2016-07-28 21:41:44,429 ERROR [NiFi Web Server-231]
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at
org.apache.nifi.web.api.dto.EntityFactory.createConnectionEntity(EntityFactory.java:251)
~[classes/:na]
at
org.apache.nifi.web.StandardNiFiServiceFacade.deleteConnection(StandardNiFiServiceFacade.java:858)
~[classes/:1.0.0-SNAPSHOT]
at
org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke(<generated>)
~[classes/:1.0.0-SNAPSHOT]
> Clustering - Merge all responses based on authorization
> -------------------------------------------------------
>
> Key: NIFI-1876
> URL: https://issues.apache.org/jira/browse/NIFI-1876
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Each node in a cluster may have a different view of the authorization access
> policies simply to in the timing of updates. Because of this, all requests
> need to be merged accordingly.
> Requests are directed at a specific resource. These would result in some 403
> responses.
> Some requests are contain a filtered view of a number of resources. These
> would need to be updated to return the most restrictive set of responses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
