Hi David
It's also possible to configure authorizers.xml to both handle LDAP and
local users (file-access) so you can have both. It's using
composite-configurable-user-group-provider. Just remember that nifi is case
sentitive, so the what you specify as the user, should match exactly what
nifi see
Mike and Shawn, thanks for the feedback, have not had a chance to try
either, but appreciate your help. Will be trying the cert this week, will
reach out to the AD managers about a more direct AD solution.
Dave
On Sat, Oct 29, 2022 at 7:10 PM Mike Thomsen wrote:
> David,
>
> Another option yo
David,
Another option you might want to explore is having AD generate client
certificates for your users.
On Sat, Oct 29, 2022 at 12:01 PM Shawn Weeks wrote:
>
> NiFi should always accept a cert at the rest api if you provide one. If your
> using curl just add the “--key” and “--cert” and call
NiFi should always accept a cert at the rest api if you provide one. If your
using curl just add the “--key” and “--cert” and call whatever api url your
trying directly. You’ll need to make sure that the cert your using is signed by
the same local CA that NiFi is set to trust and that you’ve add
Hi all,
We have a 3 node cluster secured with Microsort AD for the first time.
I need access to the REST api. The nifi-api/access/token does not work in
this case.
We did use a local CA for certificate generation on the servers.
I am reading that it is possible to do certificate based auth to