Tried this approach but it did not work. Incognito mode also does not work.
Best, Xiaozhen Liu > On May 11, 2026, at 13:36, Yicong Huang <[email protected]> wrote: > > For the JWT issue, it was sort of expected. Previously config service was > allowed for access without any permission. Now we check the permission > correctly. If your browser has an invalid JWT token, it will reject your > access. For a quick solution, can you try clean your JWT from local cache and > try again? > > Best, > Yicong Huang > [email protected] <mailto:[email protected]> > On May 11, 2026 at 12:54 PM -0700, Xiaozhen Liu <[email protected] > <mailto:[email protected]>>, wrote: >> +1 on the JWT problem. >> >> >> Best, >> Xiaozhen Liu >> >> >> >>> On May 11, 2026, at 12:52, Ryan Zhang <[email protected]> wrote: >>> >>> I was able to resolve this for now by removing package-lock.json and running >>> yarn install again. However now I am running into a different issue with >>> the JWT authentication in ConfigService: >>> >>> ERROR [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtParser$: Failed >>> to parse JWT: JWT >>> (claims->{"sub":"texera","userId":1,"googleId":null,"email":"texera","role":"ADMIN","googleAvatar":null,"exp":1777324924}) >>> rejected due to invalid claims or other invalid content. Additional >>> details: [[1] The JWT is no longer valid - the evaluation time >>> NumericDate{1778527988 -> May 11, 2026, 12:33:08 PM PDT} is on or after the >>> Expiration Time (exp=NumericDate{1777324924 -> Apr 27, 2026, 2:22:04 PM >>> PDT}) claim value (even when providing 30 seconds of leeway to account for >>> clock skew).] >>> ERROR [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtParser$: Failed >>> to parse JWT: JWT >>> (claims->{"sub":"texera","userId":1,"googleId":null,"email":"texera","role":"ADMIN","googleAvatar":null,"exp":1777324924}) >>> rejected due to invalid claims or other invalid content. Additional >>> details: [[1] The JWT is no longer valid - the evaluation time >>> NumericDate{1778527988 -> May 11, 2026, 12:33:08 PM PDT} is on or after the >>> Expiration Time (exp=NumericDate{1777324924 -> Apr 27, 2026, 2:22:04 PM >>> PDT}) claim value (even when providing 30 seconds of leeway to account for >>> clock skew).] >>> WARN [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtAuthFilter: >>> Invalid JWT: Unable to parse token >>> WARN [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtAuthFilter: >>> Invalid JWT: Unable to parse token >>> INFO [2026-05-11 19:33:08,264] org.eclipse.jetty.server.RequestLog: >>> [0:0:0:0:0:0:0:1] - "GET /api/config/user-system HTTP/1.1" 401 >>> INFO [2026-05-11 19:33:08,264] org.eclipse.jetty.server.RequestLog: >>> [0:0:0:0:0:0:0:1] - "GET /api/config/gui HTTP/1.1" 401 >>> >>> I found this possible related PR: >>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fgithub.com%2Fapache%2Ftexera%2Fpull%2F4903__%3B!!CzAuKJ42GuquVTTmVmPViYEvSg!PhFPsSR_Pi1Vx1e5eILzfY9b8rbc3ue4u25FPfup7kxRx-UaIyRhfYES8us1s_xb6jXHaOT_QN0_TPqsGyA%24&data=05%7C02%7Cyiconghuang%40umass.edu%7C3275951c199f4a6a360f08deaf96f455%7C7bd08b0b33954dc194bbd0b2e56a497f%7C0%7C0%7C639141260521407244%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C60000%7C%7C%7C&sdata=bJQQse1uvDMyyzZuu5E0UNeKF%2BowbZGJoHsFgjoANhE%3D&reserved=0 >>> >>> Thanks, >>> Ryan >>> >>> >>> On Mon, May 11, 2026 at 12:20 PM Ryan Zhang <[email protected]> wrote: >>> >>>>> Hi Texera team, >>>>> >>>>> After I pulled from the latest main today, I encountered two errors >>>>> related to our dependencies for the frontend. >>>>> >>>>> The first error is related to the *tslib *version, which was resolved >>>>> when I upgraded from 2.3.1 to the latest 2.8.1. The error output was this: >>>>> >>>>> ./node_modules/ng-zorro-antd/fesm2022/ng-zorro-antd-tree.mjs:1736:19-36 - >>>>> Error: export '__runInitializers' (imported as '__runInitializers') was >>>>> not >>>>> found in 'tslib' (possible exports: __assign, __asyncDelegator, >>>>> __asyncGenerator, __asyncValues, __await, __awaiter, >>>>> __classPrivateFieldGet, __classPrivateFieldSet, __createBinding, >>>>> __decorate, __exportStar, __extends, __generator, __importDefault, >>>>> __importStar, __makeTemplateObject, __metadata, __param, __read, __rest, >>>>> __spread, __spreadArray, __spreadArrays, __values) >>>>> >>>>> The second error is a dependency conflict between monaco-breakpoints and >>>>> monaco-editor which I have not been able to resolve. When installing, I >>>>> get this error: >>>>> >>>>> npm error code ERESOLVE >>>>> npm error ERESOLVE unable to resolve dependency tree >>>>> npm error >>>>> npm error While resolving: [email protected] >>>>> npm error Found: [email protected] >>>>> npm error node_modules/monaco-editor >>>>> npm error monaco-editor@"npm:@codingame/[email protected]" >>>>> from the root project >>>>> npm error >>>>> npm error Could not resolve dependency: >>>>> npm error peer monaco-editor@"^0.39.0" from [email protected] >>>>> npm error node_modules/monaco-breakpoints >>>>> npm error monaco-breakpoints@"0.2.0" from the root project >>>>> >>>>> Has anyone else encountered this error or know a solution? >>>>> >>>>> Thanks, >>>>> Ryan
