WireGuard Portal exposure: external identity is not the same as authorization
WireGuard Portal exposure: external identity is not the same as authorization
Tag archive
WireGuard Portal exposure: external identity is not the same as authorization
AI ecosystems need federation that preserves issuer, actor, delegation, and local policy instead of treating every external token as portable trust.
For a long time qcontroller had no idea who was talking to it. That was fine while it ran on my...
How to constrain GitHub Actions OIDC trust with tested subject and audience claims.
On November 30, 2026, Vercel starts labeling some Marketplace vendors "Not secure." If your API still...
Vercel is giving Marketplace vendors until January 2027 to replace long-lived API keys with OIDC and short-lived tokens or risk being delisted. Developers point out that Vercel's own GitHub Actions deployment guide still authenticates with a persistent VERCEL_TOKEN secret.
Step-up authentication means the user signs in with something cheap (a password, a passkey on a...
1. Introduction: Why Storing Tokens in the Browser is Dead For years, the standard...

Introduction In my previous posts, I mentioned the important topic of zero static...
How to import Supabase users and their existing bcrypt password hashes into Keycloak on Open Source Cloud, so nobody has to reset a password.
GitHub has extended npm trusted publishing to cover dist-tag changes under short-lived OIDC credentials, but the new permission ships off by default on every configuration.
Enterprise SSO is a federation of trust, not one shared login session. SAML or OIDC carries identity proof, while each application still owns its session and authorization.