A minimal ASP.NET Core app embedding Duende IdentityServer, configured for the same servicecontrol-api audience the Keycloak path uses. Same SPA flow, different IdP, more code.
The four values that change when you swap identity providers, the audit instance that mirrors them, the forwarded headers ServiceControl trusts behind a reverse proxy, and the moment the browser finally lands back in ServicePulse with a token.
A realm, a client scope, the audience mapper that catches every first-time setup, and the public client ServicePulse uses to redirect through Keycloak.
ServiceControl 6.13 lets ServicePulse sit behind any OpenID Connect identity provider. This series wires it to Keycloak in Docker, end to end, on a home server.
Two fixes after the series - letting Claude run without interruptions inside Docker, and a git-wtadd bug that was silently pushing commits to main
OpenCode looked great on paper. After a week of daily use, I'm going back to Claude Code.
Container naming, terminal quirks, smarter worktrees, and the principle behind it all
When a second AI tool exposes every assumption baked into your launcher scripts
A series on running AI coding tools in a containerized development environment on Windows
Teaching an AI agent your conventions so it can actually follow them
How I keep my Windows machine clean by stuffing all development tools into a Docker container