Thanks!
Em qua., 18 de mar. de 2020 às 19:42, Andy LoPresto
escreveu:
> My Python is not great but I would look at NiPyAPI as an example and the
> NiFi REST API [1] to see how objects are nested. The ProcessorConfigDTO [2]
> contains a dict of str: PropertyDescriptorDTO at descriptors, so you co
My Python is not great but I would look at NiPyAPI as an example and the NiFi
REST API [1] to see how objects are nested. The ProcessorConfigDTO [2] contains
a dict of str: PropertyDescriptorDTO at descriptors, so you could iterate over
that as you’re asking. For example, the list_sensitive_proc
Yeah, I've read all of that and I have a semi-working configuration. The
problem is that when using OpenID tokens (oidc) in a clustered
configuration, the node that requests the authentication is the only one
that can validate it. If a user authenticates to node-1, but then later
node-2 gets a re
Hi folks,
I'm trying to write a quick python InvokeProcessorScript where I need to
iterate over all Dynamic Properties from the processor to select just a few
and I'm having some difficulties with the class types between Jython and
Java.
Can someone show me how to iterate over "context.properties
Wyllys,
NiFi is comprised of any number of web applications. NiFi offers extension
points for custom processor configuration UIs and data type viewers. These
UIs can be bundled and discovered at runtime. These docs [1] detail the
steps necessary for proxying a NiFi instance.
Thanks
Matt
[1]
htt
I'm surprised you haven't had lots of requests for this already. As it
stands now, I cannot figure out how to configure a secure cluster behind a
reverse proxy (for example, in a kubernetes environment behind an nginx
ingress) that also incorporates OpenID authentication from an external
service.
Hi Wyllys,
As I started reading, I was going to suggest the proxy approach. Unfortunately,
at this time I am unaware of any way to change the paths within NiFi itself -
there would be substantial refactoring required to make that an option. You can
open a feature request Jira for that, or perha
Is there a way to configure nifi to use a different root directory for web
requests?
We would like everything to be under a common root such as:
/XXX/nifi/...
/XXX/nifi-api/...
Having to proxy 2 (/nifi and /nifi-api) paths makes it very difficult to
setup a reverse proxy that also can incorporate
