🐛 Bug Report: JWT still valid after Session Timeout

Not specified by the original author.

TL;DR

Issue appwrite/appwrite#8000 (closed, 69 comments): ### 👟 Reproduction steps I use JWT to authenticate a user on my API server. I use the /account endpoint to verify the JWT.

Steps

1. Issue appwrite/appwrite#8000 (closed, 69 comments): ### 👟 Reproduction steps I use JWT to authenticate a user on my API server. I use the /account endpoint to verify the JWT. If the user is logged out because the session has expired, the JWT is still valid and I still get a successful response when I call /account with the user's JWT. ### 👍 Expected behavior The JWT should be invalid after the user is logged out and calling /account with users JWT should throw an error.
2. JWTs stayed valid after session timeout because the /account endpoint verified the JWT without checking session expiry. This is fixed upstream: the fix is live on Appwrite Cloud and ships in the next community edition release. If you self-host, upgrade to the release containing the fix. After the fix, calling /account with a JWT from an expired or logged-out session is rejected as expected.

When to use

You are seeing this: Verified against the closed issue and the maintainer/accepted answer there. Use this skill when you run into "🐛 Bug Report: JWT still valid after Session Timeout".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

If the user is logged out because the session has expired, the JWT is still valid and I still get a successful response when I call /account with the user's JWT. ### 👍 Expected behavior

Sources

• https://github.com/appwrite/appwrite/issues/8000

In https://github.com/appwrite/appwrite/issues/8000, the reporter asked: Issue appwrite/appwrite#8000 (closed, 69 comments): ### 👟 Reproduction steps I use JWT to authenticate a user on my API server. I use the /account endpoint to verify the JWT. If the user is logged out because the session has expired, the JWT is still valid and I still get a successful response when I call /account with the user's JWT. ### 👍 Expected behavior The JWT should be invalid after the user is logged out and calling /account with users JWT should throw an error. The verified answer: JWTs stayed valid after session timeout because the /account endpoint verified the JWT without checking session expiry. This is fixed upstream: the fix is live on Appwrite Cloud and ships in the next community edition release. If you self-host, upgrade to the release containing the fix. After the fix, calling /account with a JWT from an expired or logged-out session is rejected as expected. Source thread: https://github.com/appwrite/appwrite/issues/8000