Replies: 8 comments
-
I am working with @carthick on this issue that we need help on - to be more clear, we are using a Bearer transport and Database strategy like so:
with the routers defined as such:
We can successfully register and verify users - running into this issue with login, which we know is supposed to be form data. |
Beta Was this translation helpful? Give feedback.
-
Have you tried out from the Swagger UI (likely on |
Beta Was this translation helpful? Give feedback.
-
Just tried it via swagger documentation via the Authorize button - it says |
Beta Was this translation helpful? Give feedback.
-
Check if you have another router with the prefix |
Beta Was this translation helpful? Give feedback.
-
The only other endpoint of /auth/db/ is /auth/db/logout; there's no other routers that have that. |
Beta Was this translation helpful? Give feedback.
-
@frankie567 Do we need to change anything in the code |
Beta Was this translation helpful? Give feedback.
-
I don't see anything wrong with what you showed me. I tried on my side and it works correctly. Without seeing the whole project, it's hard to see where the problem might come from. Try to disable your own routers, middlewares and other things that might get in the way. |
Beta Was this translation helpful? Give feedback.
-
We found the issue (thanks for pointing out middleware) - we had a Sanitation Middleware that was interfering with it. Disabling the middleware allowed it to start working again. |
Beta Was this translation helpful? Give feedback.
-
Hi,
We are trying to implement login feature using something similar to the below code....
But we are getting 422 error when hitting the api...
Here is the error we are getting
Please let us know what would be the fix for this.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions