Commit 78b3328
committed
revert(clerk-js): remove cookie write monotonic guard
The cookie write guard at AuthCookieService.updateSessionCookie was
causing integration test failures across handshake, sessions, and
multiple framework matrices. The guard would reject token writes when
oiat+iat matched, but two tokens with identical timestamps can still
differ in OTHER claims (azp added in a recent token-format rollout,
org_id, etc.). Backend then logged 'Session token from cookie is
missing the azp claim' and treated the session as invalid, redirecting
to /sign-in.
The broadcast handler (tokenCache.ts:292) and Session resource
(Session.ts:463, :526) keep the monotonic enforcement at the layers
where it works correctly. The cookie chokepoint was too aggressive.
The cookie path
deserves a guard but with a different shape (e.g., raw-string equality
or signature compare), not the claim-timestamp shape.1 parent d265058 commit 78b3328
1 file changed
Lines changed: 0 additions & 23 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
16 | | - | |
17 | 16 | | |
18 | 17 | | |
19 | 18 | | |
20 | 19 | | |
21 | 20 | | |
22 | | - | |
23 | 21 | | |
24 | 22 | | |
25 | 23 | | |
| |||
196 | 194 | | |
197 | 195 | | |
198 | 196 | | |
199 | | - | |
200 | | - | |
201 | | - | |
202 | | - | |
203 | | - | |
204 | | - | |
205 | | - | |
206 | | - | |
207 | | - | |
208 | | - | |
209 | | - | |
210 | | - | |
211 | | - | |
212 | | - | |
213 | | - | |
214 | | - | |
215 | | - | |
216 | | - | |
217 | | - | |
218 | | - | |
219 | | - | |
220 | 197 | | |
221 | 198 | | |
222 | 199 | | |
| |||
0 commit comments