Lab

Cilium Gateway API: External Authentication

Add SSO and JWT-based authentication to your services using Gateway API

Learn how to use the Gateway API HTTPExternalAuthFilter (GEP-1494) with Cilium
to add authentication in front of any Kubernetes service — without modifying the
application itself.

In this lab, you will:

  • Protect an HR dashboard with Authelia single sign-on (cookie-based)
  • Authorize a machine-to-machine workflow (the Monday-morning headcount report) using OIDC bearer tokens
  • Fine-tune which headers the authorizer sees and which identity headers reach your app
  • Give an AI agent scoped access to an MCP server with the same authorizer
  • Apply what you've learned by securing the app for both humans and a read-only agent in the exam

We recommend completing the introductory
Cilium Gateway API lab first.

  • 🏛️ The Lab Environment

    Meet the HR dashboard and the (currently absent) authentication

  • 🔐 Protect the HR Dashboard with Authelia SSO

    Put single sign-on in front of the dashboard using HTTPExternalAuthFilter

  • 🤖 Let the Headcount Report Through with an OIDC Bearer Token

    Authorize the Monday-morning machine-to-machine job with a Keycloak-issued JWT

  • 🔐 From Authentication to Authorization

    The gateway proves who you are; the app decides what you can see. Watch an intern and HR Ops get different views of the same dashboard

  • 🤖 Give an AI Agent Access via MCP

    Gate a Finance AI agent at the same Cilium filter — with its own machine identity

  • 🎓 Exam: Secure the App for Humans AND a Read-Only Agent

    Author one HTTPRoute that gates two very different clients — and prove least privilege