denoland / denoland/deploy_feedback

Unexpected change of JWT Key

Open
#237 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Maybe because Deno Deploy is not running on a single server, the jwt key I created will change from time to time, resulting in unexpected jwt token invalidation. Tokens generated with the old key will be invalid after the key is updated.
```ts
export const jwtKey = await crypto.subtle.generateKey(
{ name: "HMAC", hash: "SHA-512" },
true,
["sign", "verify"],
);
````
Not sure if there is any specific way to solve it.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the crypto.subtle.generateKey snippet in the issue and investigate how generated keys behave across Deno Deploy instances and restarts. Reproduce whether tokens signed with an earlier key become unverifiable, then document the supported way to retain or share the JWT key, or clearly record the platform limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
deno, typescript
Domain
authentication, cloud, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.