Skip to content

Require generated clients to forward the user JWT - #171

Merged
jasonzbao merged 2 commits into
mainfrom
rishikesh/forward-app-user-jwt
Sep 24, 2026
Merged

jasonzbao merged 2 commits into
mainfrom
rishikesh/forward-app-user-jwt

Conversation

@rishikesh-major

Copy link
Copy Markdown
Collaborator

Why

App coders have been constructing PostgresResourceClient by hand with only MAJOR_JWT_TOKEN, including for webhooks and cron routes. A resource call to go-api without x-major-user-jwt will be rejected. cron.json is no longer registered.

What

  • app-builder: use the generated client. A webhook and a workflow app_call already have the user JWT. Do not add cron.json.
  • using-connectors: examples that pass only majorJwtToken are for scripts outside a request, not app code.

A hand-rolled resource client that only sets MAJOR_JWT_TOKEN is rejected on resource calls. App code must use the generated client. cron.json is not a scheduler.
The using-connectors skill is for app code. Drop the sentence that treated MAJOR_JWT_TOKEN-only clients as a valid script pattern.
@jasonzbao
jasonzbao merged commit 56a340d into main Sep 24, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants