Summary
The user is configuring authentication for their flyte-binary helm build and can authenticate through the UI, flytectl, and pyflyte. However, all workflow executions show an "UNKNOWN" status, with pod logs indicating repeated "invalid_client" authentication errors. The user is unsure if correcting the configuration will resolve the errors or if they will persist due to previous issues. They mention using both OIDC and internal authentication but suspect they need to add flyteclient for proper functionality. After some troubleshooting, the user believes they may have resolved the initial issue related to authentication but now faces workflows stuck in a "RUNNING" state for an extended period. They plan to investigate further, with a suggestion to check the timeline in the UI for potential bottlenecks.