Menu

Adding Optional OIDC Login to qcontroller: How Single Sign-On Actually Works
📰

Adding Optional OIDC Login to qcontroller: How Single Sign-On Actually Works

DEV Community: authentication·Nikita Vakula·10 days ago
#Ng281lLb
#devtoauthentication#devto#dev#office#card
Reading 0:00
15s threshold

For a long time qcontroller had no idea who was talking to it. That was fine while it ran on my laptop and the only client was me. It stopped being fine the moment the orchestrator moved to a shared machine, the web UI became reachable from the office network, and a CI job needed to create VMs on its own.

The usual answer to "who is this" in infrastructure is single sign-on through OpenID Connect (OIDC): let the identity provider you already have - Keycloak, Okta, Dex, Google - do the login, and have your service trust the result. qcontroller now supports exactly that. It is optional: no auth block in the config, no authentication, same behaviour as before.

Turning it on is a few lines of JSON. But I also wanted to understand the flow well enough to explain it without hand-waving, because most explanations I found either stop at "it's like OAuth2 but for identity" or dive straight into token formats.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.