feat(backend,nextjs): Machine-to-Machine #4875
Open
+711
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds machine to machine. Dx guide here
The spicy changes are in
/backend/src/tokens/request.ts
and/nextjs/src/server/clerkMiddleware.ts
.The changes to authenticate request adds the MachineAuthenticated and MachineUnauthenticated objects and the logic required.
In nextjs middleware specifically, I check the JWT sub claim in middleware and if it's prefixed with
mch_
, passentity: machine
to authenticateRequest. There's a few alternatives but that's the meat and potatoes of this. Discussion hereThe changes in the other fullstack frameworks are just to satisfy ts. The primary changes are for
/backend
and/nextjs
.The backend sdk helper to generate tokens is prefixed with
__internal_
because we wanted to initially roll it out internally.Also unsure about using non null assertions lol
Checklist
pnpm test
runs as expected.pnpm build
runs as expected.Type of change