Hello,
Currently OIDC is only part of authentication, and the authenticated user
identity is then passed to whatever authorizer is configured. If you wanted
to authorize any authenticated user to do anything, then you could
implement your own Authorizer that just returns approved for everything.
Hi,
I am trying to use OIDC for Authentication, but it seems to not support any
form of Authorization -- is there any way to avoid having to manually list
every user permitted after installation? ex. allow all authenticated users,
or support groups from the OIDC provider?
Thanks!
Ryan
Dont think that is a known issue/pattern we've heard much of.
Definitely will need a stack track set when you observe it. Ideally
you get a stack dump when all looks good, then a stack trace once the
freeze had started, then again after some time within the freeze
again. Share those along w
Hi all,
Our team just upgraded to NiFi 1.13.2. We've noticed frozen
relationships where data just queues up until the Remote Process Group is
started/stopped again.
I don't have any specific stacktraces isolated yet, just curious if
anyone else has experienced any issues with communication
(I'm sorry, I meant to say that I read that the Java Flight Recorder is
now available for unlicensed--in the original Oracle sense--for use.)
On 8/2/21 12:44 PM, Russell Bateman wrote:
Scott,
I believe I read somewhere in the last year. I found this:
https://developers.redhat.com/blog/2020/08
Scott,
I believe I read somewhere in the last year. I found this:
https://developers.redhat.com/blog/2020/08/25/get-started-with-jdk-flight-recorder-in-openjdk-8u
And, I used it to look into a problem I had with Apache NiFi a few years
ago. For what it's worth, my experience is recorded here:
Hello.
I may have notice something similar.
And it was a matter of disk Space for the provenance repository.
There was not enough space, and flowfile with large content
NiFi was waiting to free some spaces.
Regards
Etienne Jouvin
Le lun. 2 août 2021 à 20:20, scott a écrit :
> I'm using op
I'm using openjdk-11.0.7.10-4 as I was on the previous version of NiFi.
I'll look around for a free Java profiler to use to dig deeper.
Thanks,
Scott
On Sat, Jul 31, 2021 at 7:56 PM Joe Witt wrote:
> Scott
>
> Nope this sounds pretty dang unique
>
> What JVM? May need to attach a profiler.
>
>
Vibhath,
If you get into that state again, recommend you run:
bin/nifi.sh diagnostics diag1.txt
And then provide the generated file, diag1.txt - that will include a lot of
diagnostic information that should help understand exactly what is happening.
Thanks
-Mark
On Aug 2, 2021, at 10:01 AM,
