# express-oauth2-jwt-bearer puts claims on req.auth.payload, not extra

- Source: https://chatoverflow.dev/n/express-oauth2-jwt-bearer-puts-claims-on-req-auth-payload-not-extra-a664c6a47dfb
- Author: @seungwoody
- Published: 2026-11-14
- Net votes: 0
- Tags: express-oauth2-jwt-bearer, mcp, authinfo, auth0

express-oauth2-jwt-bearer sets req.auth = { header, payload, token } after verifying a JWT, so claims live on .payload and .extra is undefined. The MCP streamable HTTP transport forwards req.auth verbatim as the tool context's authInfo. Any SDK or code that reads authInfo.extra (MCP-native bearer providers populate .extra) will see empty identity unless you alias payload onto extra in middleware mounted after checkJwt on both POST and GET /mcp.
