[DISCUSS] Security Features Roadmap

I have created a Roadmap document on the wiki here [1]. It is a rough outline of the immediate and future security needs I see, but I would like to gather community feedback and refine and enhance what is there so far. Specifically, I know Andre Fucs de Miranda, Bryan Rosander, and Jeremy

Re: Release Guide updates preliminary review

Looks good, Joe, and thanks for the updates. Definitely glad you used your fresh perspective on things to call out those items which may have been glossed over. On Fri, Oct 21, 2016 at 12:11 PM, Andy LoPresto wrote: > Joe, > > I opened a small PR against your branch with

Re: Nifi 1.0.0 - HTTPS

If you have a chance, open up the Developer Tools in your browser and check out the response coming back from the server. Add a processor to your canvas and the response will contain an entry like this uri:" https://localhost:8443/nifi-api/processors/e82c44e1-0157-1000-73be-f709aa402a30 " This

Re: Release Guide updates preliminary review

Joe, I opened a small PR against your branch with some additional details on the checksums and GPG signatures. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Oct 21, 2016, at 11:20 AM, Joe Skora

Release Guide updates preliminary review

NiFi Devs, I have taken a first cut at the Release Guide updates mentioned in NIFI-2911 , but I'm not quite ready to submit a pull request yet as I think it needs a little more "tender loving care". If anyone has time to review it and provide any

Re: Master build failure with nifi-jolt-transform-json-ui?

That link from first email works for me now, maybe worth trying again? On Fri, Oct 21, 2016 at 10:15 AM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > This is likely a side-affect of the DDOS attack on DNS servers on the east > coast. > >

Re: Master build failure with nifi-jolt-transform-json-ui?

This is likely a side-affect of the DDOS attack on DNS servers on the east coast. http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835 Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On Friday, October 21, 2016 10:04

Re: Master build failure with nifi-jolt-transform-json-ui?

Trying to open that in a browser gives the same error and says no healthy backends, maybe the npm registry is having issues? Thanks, Bryan On Fri, Oct 21, 2016 at 10:02 AM, Joe Gresock wrote: > Is anyone else getting a build failure on master? > > [WARNING] npm WARN

Master build failure with nifi-jolt-transform-json-ui?

Is anyone else getting a build failure on master? [WARNING] npm WARN package.json nifi-jolt-transform-json-ui@ No README data [ERROR] npm http GET https://registry.npmjs.org/angular-ui-codemirror/-/angular-ui-codemirror-0.3.0.tgz [ERROR] npm http 503

Re: Nifi 1.0.0 - HTTPS

Hi, Thanks for help ! I didn't map any path of nifi. I just have a ssl termination on a load balancer ( haproxy in this case) that forward all req. that at commint to it's frontentd ( https:444 ) to the ip of the nifi instance ( which is http:8080). So user browser hits

Re: Nifi 1.0.0 - HTTPS

Hey, thanks for reaching out. There are a couple of key items to know when standing up NiFi behind a proxy. 1) NiFi is comprised of a number of web applications (web ui, web api, documentation, custom ui's, etc). So you'll need to set up your mapping to the root path. That way all context paths

Nifi 1.0.0 - HTTPS

Hi guys, I have one big issue regarding nifi over https, and just dont't have any clue to solve it. I have a nifi instance behind a balancer ( haproxy ) that does a ssl termination, by presenting a certiticate to the user, and than forward request to nifi backend over http protocol ( without