Implementing the Ory stack at Padis
summary
Padis replaces a homegrown Spring auth service with the Ory stack and reports a working production migration: Kratos for identities handles browser sessions and cookie security, Hydra tokens for ETL supply OAuth tokens to Airflow jobs, Oathkeeper as policy enforcer gates requests and calls a small middleware that multiplexes tenants and multiple Kratos/Hydra instances. Keto is in development as a PDP. Deployment uses Kubernetes and Helm with GitLab/Jenkins; result is fewer per-service JWT checks, fixed CSRF risks, and a gradual swap that keeps legacy gateway routes functioning.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:35About Padis
- 1:14Products
- 2:40Infrastructure
- 3:38System Architecture
- 4:05System Components
- 8:40Use Cases
- 10:16Pros Cons
- 13:48Current Architecture
- 18:40Implementation
related talks
18mMake Auth great again with Ory
16mHow to move your RBAC into Ory 
19mHow TIER IV Replaced Identity Server with Ory
18mRunning Ory on a 30M users platform
25m Introducing the Ory Network
41mBuilding Modern Authorization: A Practical Guide To Centralized, Distributed, and...
54mProtecting API Workloads Against OWASP and Programming Language CVE's
26mOne Auth Gateway to authenticate them all