Open engrrio07 opened 3 months ago
My Deployment had the same issue. I disabled signups.
The Objective is to disable signups so no unwanted user can signup to the instance while allowing invited users to login.
I have same issue... and my backend log from command "docker logs infisical-backend" below
{"level":50,"time":1712641055737,"pid":1,"hostname":"46f996033a09","reqId":"req-2ph","severity":"ERROR","err":{"type":"UnauthorizedError","message":"Token missing","stack":"Unauthorized access: Token missing\n at Object.
is it about Object.handler...? it contains strange path...? I think path of "verify-auth.mjs" is wrong...
(using version3 of "docker-compose.prod.yml" file)
@akhilmhdh can you please take a look at this when you have time?
For a while I thought this might be a local issue of mine but I am unable to login anymore after my docker-compose based installation has upgraded itself lately to the latest docker tag. I can't fully traceback which updated introduced it but right now I can't login with any account anymore and resetting the PW also does not work :/
Describe the bug
When new members receive an invite they get redirected to log-in page immediately instead of sign-up page and encounters
400 Bad Request
on/api/v1/auth/token
route.To Reproduce
Steps to reproduce the behavior:
Join now
token
on network requests fails with400 Bad Request
status on/api/v1/auth/token
Expected behavior
New user should be able to sign-up
Screenshots
Platform you are having the issue on:
Self-hosted infisical running on Kubernetes deployed via infisical-standalone/1.0.6 helm chart
Additional context
req.cookies.jid
is missing (reference).