-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
API: Add logout endpoint #223
Comments
/attempt |
Assigned the issue to you! |
@lakshay-saini-au8 Are you still working on this, or should I take it on? |
@rashmod you can get started with this one. It has been quite a long time since I've made the assignment |
The link for postman collection in docs in the API testing sections is broken Also, you did not assign issue to me |
I'm getting them fixed in a min. EDIT: Done fixing. |
I'm looking to test the logout API endpoint, but I noticed that we don't have a traditional email and password login—just Google and GitHub OAuth. Would I need to run the frontend to test it, or am I missing something? |
We have email+OTP auth aswell. Whenever the login is successful, we are setting the jwt token in the cookie of the response. Further requests make use of this cookie when making a request. You would need to implement a logic that will unset this cookie value. |
the precommit hook is failing because of the lining rules |
Yes, we are aware of this issue. The only way for us would be to disable the pro-commit hooks for now. But for your end, you can use --no-verify flag along with git commit to bypass hooks. |
I don't think that should be done since users wont have the option to log out before their onboarding is finished. |
Any suggestions how to tackle this problem? |
That's a feature, not a problem. Once you authenticate yourself, you would need to use the "Update User" request in Bruno and set |
Okay I got it. |
Description
Add an endpoint to log out. The functionality will be very simple - just clear the
token
cookie.Solution
@Public
to it.token
cookie.The text was updated successfully, but these errors were encountered: