lfk/frontend
2
0
Fork 0
Code Issues 3 Pull Requests Actions Projects Releases Wiki Activity

401 Unauthorized on /users/ + /tracks/ #28

New Issue
Closed
opened 2021-01-09 16:42:31 +00:00 by philipp · 1 comment
philipp commented 2021-01-09 16:42:31 +00:00
Owner
Copy Link

after approx. 5mins (access token expiry), loading the users or tracks page results in a 401 Unauthorized Error.

this issue occurs both on local dev as well as on the live system.

this is the current error dump:

XHRGEThttps://dev.lauf-fuer-kaya.de/api/users
[HTTP/2 401 Unauthorized 39ms]

    	
    name	"IllegalJWTError"
    message	"Your provided jwt could not be parsed."
    stack	"Error\n at IllegalJWTError.HttpError [as constructor] (/node_modules/.pnpm/routing-controllers@0.9.0-alpha.6_4ae0cf6eab4c30830de5e5acc43ca1c7/node_modules/routing-controllers/http-error/HttpError.js:31:23)\n at new UnauthorizedError (/node_modules/.pnpm/routing-controllers@0.9.0-alpha.6_4ae0cf6eab4c30830de5e5acc43ca1c7/node_modules/routing-controllers/http-error/UnauthorizedError.js:24:28)\n at new IllegalJWTError (/dist/errors/AuthError.js:21:9)\n at refresh (/dist/middlewares/authchecker.js:8…ode_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/route.js:112:3)\n at Layer.handle [as handle_request] (/node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/layer.js:95:5)\n at /node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/index.js:281:22\n at Function.process_params (/node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/index.js:335:12)\n at next (/node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/index.js:275:10)"

we might need to do some server side debugging/ combination of frontend+backend @niggl

after approx. 5mins (access token expiry), loading the `users` or `tracks` page results in a `401 Unauthorized Error`. this issue occurs both on local dev as well as on the live system. this is the current error dump: ``` XHRGEThttps://dev.lauf-fuer-kaya.de/api/users [HTTP/2 401 Unauthorized 39ms] name "IllegalJWTError" message "Your provided jwt could not be parsed." stack "Error\n at IllegalJWTError.HttpError [as constructor] (/node_modules/.pnpm/routing-controllers@0.9.0-alpha.6_4ae0cf6eab4c30830de5e5acc43ca1c7/node_modules/routing-controllers/http-error/HttpError.js:31:23)\n at new UnauthorizedError (/node_modules/.pnpm/routing-controllers@0.9.0-alpha.6_4ae0cf6eab4c30830de5e5acc43ca1c7/node_modules/routing-controllers/http-error/UnauthorizedError.js:24:28)\n at new IllegalJWTError (/dist/errors/AuthError.js:21:9)\n at refresh (/dist/middlewares/authchecker.js:8…ode_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/route.js:112:3)\n at Layer.handle [as handle_request] (/node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/layer.js:95:5)\n at /node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/index.js:281:22\n at Function.process_params (/node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/index.js:335:12)\n at next (/node_modules/.pnpm/express@4.17.1/node_modules/express/lib/router/index.js:275:10)" ``` we might need to do some server side debugging/ combination of frontend+backend @niggl
philipp added this to the Base-System milestone 2021-01-09 16:42:31 +00:00
philipp added the
bug
priority:high
help wanted
 labels 2021-01-09 16:42:31 +00:00
niggl was assigned by philipp 2021-01-09 16:42:31 +00:00
philipp self-assigned this 2021-01-09 16:42:31 +00:00
philipp added the
confirmed
 label 2021-01-09 16:43:19 +00:00
niggl commented 2021-01-09 18:07:02 +00:00
Owner
Copy Link

Works on the dev.lfk stage but not on localhost.
Reason: Cookies apparently aren't designed for tlds and localhost is a tld
Workaround: Call the frontend on 127.0.0.1 instead of localhost.

Works on the dev.lfk stage but not on localhost. Reason: Cookies apparently aren't designed for tlds and localhost is a tld Workaround: Call the frontend on 127.0.0.1 instead of localhost.
niggl closed this issue 2021-01-09 18:07:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
confirmed
The reported bug has been confirmed
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
priority:high
priority:low
priority:medium
question
More information is needed
status:blocked
status:doing
status:review_needed
wontfix
This won't be fixed
Complexity
Easy
The complexity is low
Complexity
Hard
The complexity is high
Complexity
Medium
The complexity is medium
Kind/Bug
Something is not working
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Question
A question
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status/Confirmed
This is indeed a bug/issue
Status
Doing
Somebody is working on this
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Status
Review needed
Needs a reveiw
No Label
bug
confirmed
help wanted
priority:high
Milestone
No items
No Milestone Base-System
Projects
Clear projects
No project
Assignees
Clear assignees
niggl odit_bot philipp
No Assignees niggl philipp
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lfk/frontend#28
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?