Tagged “identity”

4 posts · View all tags
The wrong valid token: authenticating an MCP tools server with authentik
IntermediatePart 6

The wrong valid token: authenticating an MCP tools server with authentik

Agent orchestration part 4 scoped tools in the client and admitted the server still trusted whoever reached the port. This puts a JWT verifier in front of it, with its own authentik client, so the tools server refuses anonymous callers — and refuses the gateway's own valid token, because a separate provider means a separate issuer. Includes the documented client-credentials helper that cannot work here, and the four silent 404s it produces instead of saying so.

Agentsself-hostingmcpsecurity
September 10, 202616 min read
Read more
The key that expires: giving an agent its own identity at the gateway
IntermediatePart 5

The key that expires: giving an agent its own identity at the gateway

Part 4 ended with a shell, a static key and a model that answered. This replaces that key with a token your identity provider issues, that carries a scope, and that dies after five minutes. authentik issues it over client credentials, the gateway verifies it in twenty-five lines, and three status codes prove the boundary. Includes the requirement authentik doesn't document, and the licence wall you hit if you follow LiteLLM's own guide.

Agentsgatewaylitellmsecurity
September 8, 202618 min read
Read more
The binding that wasn't there: group access control, and what SSO doesn't protect
IntermediatePart 4

The binding that wasn't there: group access control, and what SSO doesn't protect

Part 3 shipped SSO with empty bindings. Closing that gap on the LiteLLM gateway turned up something worse: authentik's wizard let us configure the bindings, showed them in its own table, and saved none of them — no error, no warning. Then, once access control actually worked, the API answered a request from a shell with no account, no session and no membership. Both of those are the post.

gatewaylitellmsecurityhardening
September 3, 202615 min read
Read more
One login for everything: putting authentik in front of a self-hosted app
IntermediatePart 3

One login for everything: putting authentik in front of a self-hosted app

Part 2 fixed how containers run. This fixes who gets to log in. Deploy authentik as your own identity provider, connect Langfuse to it over OIDC, and understand the pieces — provider, application, redirect URI, scopes — instead of copying a config. Includes the two failures a real run produced: a compose file that silently swallows your settings, and OAuthAccountNotLinked.

self-hostingsecuritylangfusehardening
September 2, 202618 min read
Read more