🔐 [FEATURE] [1.0] Authentication & Authorization

Is your feature request related to a problem?

Enterprise customers require authenticated dashboards and fine-grained access controls, but Flock currently trusts everyone with access to the process. There is no supported OAuth/OIDC integration or API key system, making it impossible to deploy in regulated environments.

Describe the solution you want to see

• Provide pluggable authentication modules for the dashboard (OAuth2/OIDC) and API (API key + secret stores) with configuration via environment variables or config files.
• Implement role-based authorization that maps dashboard/API actions and agent visibility to user roles or labels.
• Emit audit logs for login events, access denials, and privileged actions to satisfy compliance requirements.
• Supply end-to-end examples demonstrating integration with popular identity providers (Auth0, Azure AD, Okta).

Describe alternatives you have considered

Teams can front the dashboard with custom reverse proxies, but that only guards HTTP access and doesn’t integrate with Flock’s visibility model or API usage. Building auth in each deployment slows adoption and increases support burden.

Additional context

Make sure the solution interplays with visibility rules (Private/Tenant/Labelled) so agent permissions stay coherent. Coordinate rollout alongside the Kubernetes chart (#279) for turnkey enterprise deployments.

Start by mapping the dashboard and API entry points, then review the existing Private, Tenant, and Labelled visibility rules and the Kubernetes chart in issue #279. Define the authentication, role mapping, audit logging, and identity-provider example scope before implementation; done means these pieces work coherently for dashboard and API access.