fix: ensure we always release the claim refresh lock

supertokens · May 23, 2024 · 181853a · 181853a
1 parent 87d9140
commit 181853a
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 8 deletions.
diff --git a/bundle/bundle.js b/bundle/bundle.js
diff --git a/lib/build/recipeImplementation.js b/lib/build/recipeImplementation.js
diff --git a/lib/ts/recipeImplementation.ts b/lib/ts/recipeImplementation.ts
@@ -243,10 +243,12 @@ export default function RecipeImplementation(recipeImplInput: {
                 logDebugMessage("validateClaims: trying to acquire claim refresh lock");
                 const claimRefreshLock = await lockFactory.acquireLock(CLAIM_REFRESH_LOCK_NAME);
                 if (claimRefreshLock) {
-                    accessTokenPayload = await this.getAccessTokenPayloadSecurely({ userContext: input.userContext });
-                    logDebugMessage("validateClaims: claim refresh lock acquired");
-                    // to sync across tabs. the 1000 ms wait is for how much time to try and acquire the lock
                     try {
+                        accessTokenPayload = await this.getAccessTokenPayloadSecurely({
+                            userContext: input.userContext
+                        });
+                        logDebugMessage("validateClaims: claim refresh lock acquired");
+                        // to sync across tabs. the 1000 ms wait is for how much time to try and acquire the lock
                         for (const validator of input.claimValidators) {
                             if (await validator.shouldRefresh(accessTokenPayload, input.userContext)) {
                                 try {