That sounds promising, that might explain the cluster window failing to display the nodes data.
Can you check if in the cluster JSON response each node has an attribute called "roles" which is a javascript Array type? I think it's ok if it's an empty array like "[]", but it must be an array. James On Sun, Dec 11, 2016 at 11:25 AM, Nicholas Hughes < [email protected]> wrote: > I take that back... there is one: > > TypeError: y.roles.includes is not a function > > -Nick > > > On Sun, Dec 11, 2016 at 2:22 PM, Nicholas Hughes < > [email protected]> wrote: > >> James, >> >> I just have some 304 "not modified" codes. No errors. >> >> >> >> -Nick >> >> >> On Sun, Dec 11, 2016 at 1:35 PM, James Wing <[email protected]> wrote: >> >>> Nick, >>> >>> Are there any errors shown in the Javascript console of your browser >>> developer tools? >>> >>> >>> Thanks, >>> >>> James >>> >>> On Sun, Dec 11, 2016 at 8:49 AM, Nicholas Hughes < >>> [email protected]> wrote: >>> >>>> I'm seeing some interesting behavior in a secured NiFi cluster, and I >>>> can't seem to track down what authorization pieces I might be missing. >>>> >>>> First, I'm the Initial Admin Identity... so I should have access to >>>> view/modify "all the things" (or at least give myself access to them if >>>> something is missing by default). >>>> >>>> I stood up a three node HDF 2.0.1 cluster running Apache NiFi 1.0.0 and >>>> all nodes seem to be connected (as shown on the main UI screen): >>>> >>>> >>>> >>>> ...and functioning properly in that changes on one UI show up on the >>>> other nodes. However, I cannot obtain more information about the cluster, >>>> such as the identity of the primary node, because the cluster management >>>> screen shows "Displaying 0 of" and no nodes in the list: >>>> >>>> >>>> >>>> At first I thought this might be an authorization problem, but further >>>> investigation using browser developer tools show the API response is >>>> working just fine: >>>> >>>> >>>> >>>> ...which is pretty confusing. Does anybody have any idea if I'm doing >>>> something wrong or if there was an issue in 1.0.0 which would cause this >>>> behavior? >>>> >>>> Thanks! >>>> >>>> Nick >>>> >>>> >>>> >>> >> >
