SqlOS 4.1: Any Port on the Loopback
SqlOS now matches loopback redirect URIs per RFC 8252 §7.3, so Codex, ChatGPT desktop, and other native MCP clients complete OAuth against your server without registering a port in advance.
Blog
Auth, hierarchical authorization, EF Core, and practical .NET application security — release by release.
SqlOS now matches loopback redirect URIs per RFC 8252 §7.3, so Codex, ChatGPT desktop, and other native MCP clients complete OAuth against your server without registering a port in advance.
Authorized lists now start from one method — BuildFilterAsync — and compose with ordinary EF Core for pagination, sorting, search, and projection.
Discovery, ID tokens, UserInfo, and a consent screen — on by default. Other apps can now federate against your SqlOS host with any standard OIDC library.
Your SqlOS app is an OpenID Provider. Give any other app — Next.js, ASP.NET Core, a partner's — a sign-in button backed by your users, with one client seed and a standard OIDC library.
Empty allowlists grant nothing, every grant uses the same silent intersection, and first-party hosts can see the result.