-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Failed to find refresh token when inviting new members #1640
Comments
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... {"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. (file:///backend/dist/server/plugins/auth/verify-auth.mjs:13:11)\n at hookIterator (/backend/node_modules/fastify/lib/hooks.js:405:10)\n at next (/backend/node_modules/fastify/lib/hooks.js:239:18)\n at handleResolve (/backend/node_modules/fastify/lib/hooks.js:250:7)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)","name":"Unauthorized access"},"msg":"Token missing"} is it about Object.handler...? it contains strange path...? (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. |
Any Fix Available Here? |
The issues mentioned in this thread are similar but a bit different from one another. I suggest creating a separate issue if your bug is not the same as @engrrio07. Can you please share a screenshare using Loom @engrrio07, we are unable to reproduce on our end |
I just had the same issue using My situation is that I need to restrict sign-ups to only my company's email domain. I wanted to set the "INVITE_ONLY_SIGNUP" environment variable, but it didn't seem to work. So I did this instead:
This worked for me. |
I can reconfirm this issue on the current release (v0.82.1-postgres) in a compose deployment. The backend logs are the following:
|
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).The text was updated successfully, but these errors were encountered: