[Core feature] Migrate/Implement FlyteAdmin Grpc Auth services

[EngHabu]

Motivation: Why do you think this is important?

Goal: What should the final outcome look like, ideally?

Describe alternatives you've considered

Propose: Link/Inline OR Additional context

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

FlyteAdmin already implements authentication using OAuth2 and OpenID Connect, supporting both REST and gRPC APIs. The authentication system is designed to track and audit user actions, and FlyteAdmin can be configured to use various identity providers. However, while authentication is supported, there is no standard, open-source implementation of fine-grained authorization (AuthZ) or RBAC in FlyteAdmin as of now. Some community discussions and RFCs have proposed enhancements, but these are not yet part of the mainline project. Alternatives, such as custom middleware or external proxies, have been considered and implemented in private forks, but are not officially supported upstream. For more details, see the discussion in the referenced issues and blog posts.

If you need more detail on the current authentication mechanisms, configuration, or the status of RBAC/authorization features, let me know.

Sources:

• GitHub Issue: Enhance Flyteadmin authentication and authorization
• GitHub Issue: Access control on who can run/view workflows
• GitHub PR: Flyte Admin RBAC + Project/Domain Isolation

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!