msgbyte / msgbyte/tianji

Error: no matching decryption secret

Open
#110 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.1k
Forks
194
Avg merge
18m
Merged PRs (30d)
3

Description

what could this error be?

`[auth][error] JWTSessionError: Read more at https://errors.authjs.dev#jwtsessionerror

[auth][cause]: Error: no matching decryption secret

at jwtDecrypt.clockTolerance (file:///app/tianji/node_modules/.pnpm/@auth+core@0.34.1_nodemailer@6.9.8/node_modules/@auth/core/jwt.js:76:15)

at async flattenedDecrypt (file:///app/tianji/node_modules/.pnpm/jose@5.6.3/node_modules/jose/dist/node/esm/jwe/flattened/decrypt.js:92:15)

at async compactDecrypt (file:///app/tianji/node_modules/.pnpm/jose@5.6.3/node_modules/jose/dist/node/esm/jwe/compact/decrypt.js:15:23)

at async jwtDecrypt (file:///app/tianji/node_modules/.pnpm/jose@5.6.3/node_modules/jose/dist/node/esm/jwt/decrypt.js:5:23)

at async Object.decode (file:///app/tianji/node_modules/.pnpm/@auth+core@0.34.1_nodemailer@6.9.8/node_modules/@auth/core/jwt.js:67:25)

at async Module.session (file:///app/tianji/node_modules/.pnpm/@auth+core@0.34.1_nodemailer@6.9.8/node_modules/@auth/core/lib/actions/session.js:17:29)

at async AuthInternal (file:///app/tianji/node_modules/.pnpm/@auth+core@0.34.1_nodemailer@6.9.8/node_modules/@auth/core/lib/index.js:35:24)

at async Auth (file:///app/tianji/node_modules/.pnpm/@auth+core@0.34.1_nodemailer@6.9.8/node_modules/@auth/core/index.js:109:34)

at async getAuthSession (file:///app/tianji/src/server/dist/src/server/model/auth.js:118:22)

at async Array.<anonymous> (file:///app/tianji/src/server/dist/src/server/ws/index.js:30:33)

[auth][details]: {}

[Socket] Authenticated throw error: Error: Can not get user info.

at Array.<anonymous> (file:///app/tianji/src/server/dist/src/server/ws/index.js:32:27)`

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the authentication flow referenced in src/server/dist/src/server/model/auth.js and the WebSocket entry point in src/server/dist/src/server/ws/index.js. Trace the session decode path around the reported @auth/core JWTSessionError and determine the missing context needed to reproduce it. Done means identifying a confirmed cause and a scoped fix or documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, backend
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.