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

jwt/verification

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.

JWKS endpoint for token verification

The /api/auth/jwks endpoint returns the public key(s) needed to verify JWT tokens. The public key can be cached indefinitely as it is not subject to frequent changes. The endpoint returns a JSON object with a 'keys' array containing objects with properties: crv (Ed25519), x (public key value), kty (OKP), and kid (key ID).

JWT token verification with jose library and remote JWKS

Use jwtVerify and createRemoteJWKSet from 'jose' library to verify tokens. The issuer and audience should match the BASE_URL. Example: const JWKS = createRemoteJWKSet(new URL('http://localhost:3000/api/auth/jwks')); const { payload } = await jwtVerify(token, JWKS, { issuer: 'http://localhost:3000', audience: 'http://localhost:3000' });

JWT token verification with jose library and local JWKS

Use jwtVerify and createLocalJWKSet from 'jose' library to verify tokens with locally stored JWKS. Pass the stored JWKS object to createLocalJWKSet. The issuer and audience should match the BASE_URL.

Give your agent this brain