two questions: 1. how can I communicate user identity to flyte when using the pyflyte CLI to run a workflow? we currently are directly connecting to flyte without authorization enabled within a private VPC. I want someway to pass the current user’s $USER into flyte and filter executions based on different user aliases 2. we currently use a reverse proxy for authentication when accessing flyte console outside of the VPC. how can I have my reverse proxy convey the current user identity to flyte? is there a way to pass a HTTP Header with this information?

https://www.union.ai/docs/flyte/deployment/flyte-configuration/configuring-authentication/ • you can use Okta or other identity providers for auth

we use a reverse proxy in front of flyte http that handles our internal authentication

If you follow the docs the above you shouldn’t need the reverse proxy anymore no?

we don't want traffic to hit flyte at all until it goes through our authentication proxy. we have a fairly bespoke setup at our company

@curved-whale-1505 then you can supply a custom

--principal

is there a way in the UI to see the principal/user per execution in the table and filter on it? if not, would you be open to a contribution adding this?

yes

hey @freezing-airport-6809, I'm having trouble finding this

--principal

flag - looks like it was supported in the old

flyte-cli

here but I can't find this flag in

pyflyte