When Apache NiFi is in secure mode, each request to NiFi needs to contain the authentication information to allow the request to succeed. This can be accomplished by sending a client certificate with each request, or by exchanging LDAP or Kerberos credentials initially and receiving a JWT access token which is passed in a header on subsequent requests. I recommend using your browser’s Developer Tools feature to watch the initial interaction with NiFi via the UI to understand the request sequence that is made to accomplish this.
Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Feb 16, 2018, at 7:11 AM, Sean Marciniak <[email protected]> wrote: > > Hey team. > > I would like to be able to access NiFi's RESTful api while it is in secure > mode. > What am I required to do to make this happen? > Is there additional headers I need to set? > Do I need to have my own truststore/keystore that is shared with NiFi? > > I am currently using a groovy implementation that works if NiFi is talking > over http, but not in https. > > Any advice would be greatly appreciated. > > Sean. > > -- > <https://www.beamery.com/> > Sean Marciniak > > [email protected] <mailto:[email protected]> > > > www.beamery.com <http://www.beamery.com/> > Are you ready for GDPR? GDPR: The Complete Guide for Recruiting Teams > <https://beamery.com/academy/gdpr-for-recruiting-teams>
signature.asc
Description: Message signed with OpenPGP using GPGMail
