nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Bean <>
Subject Re: UI display problem with policies
Date Fri, 07 Apr 2017 14:25:31 GMT

Browser is Chrome 50.0.2661.94 m
(We noticed more critical browser problems with a much older Chrome. I
think it was version 37.x. In that case, the Access Polices page would not
display at all.)

In the Console of the developer tools, I get a 404 error whenever a Policy
page tries to load and the policy does not yet exist (i.e. no users have
been addeed yet and the "Create a new policy" is displayed at the top.)
As described previously, after creating the policy and adding a user, I
return to Global Menu > Policies. The _display_ indicates the Policy page I
was last on (access counters/modify), but it displays no users despite the
fact that I just added a user. In the Console, the 404 error appears.
Again, this reinforces the notion that the page being displayed is actually
the 'access counters/view' policy and not the indicated 'access


On Fri, Apr 7, 2017 at 9:54 AM, Matt Gilman <> wrote:

> Mark,
> Can you check what browser and version you're using? Also, can you open up
> the developer tools and see if there are any client side errors?
> Thanks
> Matt
> On Fri, Apr 7, 2017 at 8:51 AM, Mark Bean <> wrote:
> > On the Global Menu, the item Counters is grayed out because the user is
> not
> > on the 'access counters' policy
> > To to: Global Menu > Policies > access counters/modify
> > Create a new policy (one did not exist yet)
> > Add the user
> > At this point, the Access Policies page correctly shows the user has been
> > added to 'access counters/modify'. The authorizations.xml confirms this.
> > Next, close Access Policies window. Re-open it.
> > Global Menu > Policies
> > By default, the 'access counters/modify' page is displayed. However, this
> > is not accurate. After further testing, I believe the page that is
> actually
> > being displayed is 'access counter/view' (not modify)
> >
> > The same behavior was noted on NiFi 1.1.1 and 1.1.2. I have not
> > investigated if this occurs on other policies.
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message