Github user mcgilman commented on a diff in the pull request: https://github.com/apache/nifi/pull/2703#discussion_r194512038 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/controller/ControllerFacade.java --- @@ -1389,104 +1420,119 @@ private ProvenanceEventDTO createProvenanceEventDto(final ProvenanceEventRecord // sets the component details if it can find the component still in the flow setComponentDetails(dto); - // only include all details if not summarizing - if (!summarize) { - // convert the attributes - final Comparator<AttributeDTO> attributeComparator = new Comparator<AttributeDTO>() { - @Override - public int compare(AttributeDTO a1, AttributeDTO a2) { - return Collator.getInstance(Locale.US).compare(a1.getName(), a2.getName()); - } - }; +// try { +// AuthorizationResult result = flowController.checkConnectableAuthorization(event.getComponentId()); + AuthorizationResult result = checkConnectableAuthorization(event.getComponentId()); + if (Result.Denied.equals(result.getResult())) { + dto.setComponentType("Processor"); // is this always a Processor? + dto.setComponentName(dto.getComponentId()); + dto.setEventType("UNKNOWN"); --- End diff -- Yes, I agree. The event type should be controlled by the new provenance event policy. It is not controlled by the component policy that protects the component name and component type.
---