Empowering no code application development using Ory Kratos and Ory Keto
summary
A no-code CI/CD platform is implemented so customers design pipelines without editing repo code, migrating from GitLab runners to Tekton to avoid duplicating projects. Authentication uses Ory Kratos and authorization uses Ory Keto; engineers contribute a Kratos extension to extract user tokens needed to clone repos. A Go-based middleware layer validates sessions (cookie or gRPC metadata), fetches identity from Kratos, injects context, and an internal Keto layer enforces org/team permissions across Kubernetes clusters. The setup removes per-app auth logic and eliminates exposed GitLab instances.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 1:08Evolution of CI/CD pipelines
- 4:43Custom authentication system challenges
- 7:33Choosing Ory Kratos and Keto
- 10:44Kubernetes and token management
- 12:13Testing Ory Kratos authentication
- 14:22Integrating Ory Kratos into microservices
- 16:30Authorization with Ory Keto
related talks
18mMake Auth great again with Ory
25m Introducing the Ory Network
16mHow to move your RBAC into Ory 
24mSecuring the digital world
34mComposable Platforms: Modular Platform Engineering With Kratix and Backstage
18mRunning Ory on a 30M users platform
07mKeynote: Everything as Code: Declarative Application Delivery with GitOps Workflows- Christian Hernandez, Red Hat
38mDevelop Directly on Kubernetes with Okteto