feat(auth): extend token lifetimes for long offline gaps
CI/CD / CI · API (dotnet build + test) (push) Successful in 1m24s
CI/CD / CI · Admin API (dotnet build) (push) Successful in 1m1s
CI/CD / CI · Dashboard (tsc) (push) Successful in 1m5s
CI/CD / CI · Admin Web (tsc) (push) Successful in 37s
CI/CD / CI · Website (tsc) (push) Successful in 46s
CI/CD / CI · Koja (tsc) (push) Successful in 50s
CI/CD / Deploy · all services (push) Successful in 2m16s

A user can be offline for months (offline-first dashboard) and must stay logged
in / be able to sync on reconnect. Access 7d→30d, refresh 30d→365d, so a ~3-month
offline gap still has a valid refresh token on reconnect (queued writes sync, no
forced logout). Client only logs out on a server 401, never while offline.
This commit is contained in:
soroush.asadi
2026-06-02 23:47:06 +03:30
parent db0c3a4a02
commit 4c98c2cce1
+2 -2
View File
@@ -7,8 +7,8 @@
"Key": "meezi-dev-secret-key-min-32-chars!!",
"Issuer": "meezi",
"Audience": "meezi",
"AccessTokenExpiryDays": 7,
"RefreshTokenExpiryDays": 30
"AccessTokenExpiryDays": 30,
"RefreshTokenExpiryDays": 365
},
"App": {
"PublicBaseUrl": "https://localhost:7208",