Summary
The user is facing authentication issues with Flyte workflows triggered via gRPC/HTTPS, which began about 10 days after they were working correctly. They are receiving a log message indicating a change from the expected Client Secret method to PKCE, requiring authentication through a browser link. The user is looking for help to resolve this issue and is curious about any potential changes that may have caused this switch, despite not having modified their IDP, Azure AD. They are requesting a live session for debugging and asking about availability for the upcoming Tuesday.
kumare
are you trying to hit the endpoint using flyte remote?
kumare
there is no auth at runtime
kumare
what that is odd
kumare
I don’t think you need tokenurl etc. But I am not an auth expert. I will let David point in some direction.
But <@U079GHDNN64> what is the problem that you see. Is it that you want to use client id but it ends up using device code?
kumare
usually idps have a switch and a default
kumare
This is not pkce- this is code based flow. You have changed something on your IDP