new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Better Auth · Plugins · all subjects

oauth-provider/installation

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

OAuth Provider Plugin Installation - Mount Plugin

Add the oauthProvider to the betterAuth config with required options including loginPage (path to login page) and consentPage (path to consent page). The plugin must also be mounted alongside the jwt() plugin. Example: betterAuth({ disabledPaths: ["/token"], plugins: [jwt(), oauthProvider({ loginPage: "/sign-in", consentPage: "/consent" })] }).

OAuth Provider Plugin - Database Migration

After mounting the plugin, run either npx auth migrate or npx auth generate to add necessary fields and tables to the database.

OAuth Provider - Well-Known Endpoints Configuration

Better Auth serves OAuth Authorization Server metadata and OpenID Connect discovery metadata automatically. OAuth Authorization Server metadata is available at both {issuer}/.well-known/oauth-authorization-server and /.well-known/oauth-authorization-server/[issuer-path]. OpenID Connect discovery metadata is available at {issuer}/.well-known/openid-configuration when using openid scope. If using resource server (e.g. for MCP), add OAuth Protected Resource metadata endpoint to the API that receives access tokens.

Give your agent this brain