dj-rest-auth VS auth-module

I am using dj-rest-auth for authentication. I am using JWT token authentication. All advice on JWT tokens is to not store them in local storage. Instead, using this package I store them in HttpOnly cookie. Now, I am apparently vulnerable to CSRF attack. So I enable JWT_AUTH_COOKIE_USE_CSRF. This checks the CSRF token on authenticated requests. However, there is still the potential vulnerability known as "login CSRF" as detailed by this issue on Github. In order to account for this, there is another setting called JWT_AUTH_COOKIE_ENFORCE_CSRF_ON_UNAUTHENTICATED. This enforces CSRF on unauthenticated views (such as login).

Try to use https://github.com/iMerica/dj-rest-auth

I was using djoser in the past. Now Im using very similar dj-rest-auth https://github.com/iMerica/dj-rest-auth

you can use this.

I found the dj-rest-auth as a method of making a rest auth api, unfortunately when using the documentation I have this error coming up.

I've followed the documentation: https://dj-rest-auth.readthedocs.io/en/latest/index.html

Right now, I'm using dj-rest-auth for Token based authentication. I store token in the localStorage. Earlier I was using djoser for adding auth in the project (I wrote article about my approach with djoser).

Please use https://github.com/iMerica/dj-rest-auth as this project is no longer maintained. Thanks!

Nuxt 3 comes with built-in utilities to support session and authentication. We are working on a new official module.

The evolution of nuxt-auth: there's nuxt/auth (Nuxt 2), an alternative module to try to bridge the gap for Nuxt 3 (and another one), and suddenly, sidebase/nuxt-auth popped up, which seems to wrap next-auth. I don't know if that's the proposed official solution going forward, reuse don't reinvent, or just a stop-gap measure (will the rug get pulled again?)

If you’re on nuxt 2 you can checkout the „old“ nuxt-auth which supports google and a lot of stuff surrounding it here: https://auth.nuxtjs.org/

If this is to do with user authentication and the API is using some kind of standard way of authenticating (e.g. a REST API) I would personally use https://auth.nuxtjs.org/ to do the heavy lifting for you.

Nuxt Auth module is very convenient to configure oauth and oidc authentication. And it wires everything in a project like routes, store, Axios interceptors etc..

Documentation

https://stackoverflow.com/questions/65642232/nuxtjs-how-to-use-httponly-cookies-for-nuxt-auth-strategy https://github.com/nuxt-community/auth-module/issues/142