I second the option to disable fetchUser on init, or at least override it with my own implementation. (i need to do more complex stuff to get the user, don't ask :) )

If we have a way to overwrite fetchUser, and have access to a flag saying "isFirst" or "isInit" or something, ti seems like it would add a ton of flexibility

I would also like this feature. Since the explosion of popularity in nuxt.js, the rails/nuxt stack is exploding as well, and devise_auth_token is the most popular token solution on rails.

This developer did his own fork to adapt the auth module to devise : https://github.com/WilliamDASILVA/auth-module

Here is my workaround in plugins/axios.js

export default function ({ $axios }) {
 $axios.onRequest(config => {
 config.headers.client = window.localStorage.getItem('client');
 config.headers['access-token'] = window.localStorage.getItem('access-token');
 config.headers.uid = window.localStorage.getItem('uid');
 config.headers['token-type'] = window.localStorage.getItem('token-type');
 })
 $axios.onResponse(response => {
 if (response.headers.client) {
 localStorage.setItem('access-token', response.headers['access-token']);
 localStorage.setItem('client', response.headers.client);
 localStorage.setItem('uid', response.headers.uid);
 localStorage.setItem('token-type', response.headers['token-type']);
 }
 })

Inspired by lynndylanhurley/devise_token_auth#844 (comment)

FYI @KevinBerthier 's solution worked for me with a small tweak: You need to register axios with nuxt as a plugin:

//nuxt.config.js
....
....
plugins: [
'~/plugins/axios',
...
]
as described here

I take that back, @KevinBerthier your solution was successful in setting the right values in localStorage but for some reason, the auth-module doesnt recognize the user as having logged in. After loggin in using the above mechanism to set localStorage fields from the headers instead of the body, $nuxt.$auth.loggedIn still stays false and the auth module never makes the user autoFetch call.

When I forcibly render a token in the json body on the server side, I do get the correct behavior. So I feel like there's still a missing piece in this workaround. Any ideas?

@udit99
@KevinBerthier

I'm already also using headers.token instead of response. But this happened by Laravel backend with Set-Cookie option.

You can try workaround with setting $auth userToken by this in axios plugin

await app.$auth.setUserToken(newToken) 

This will try to update $auth token globally and will refetch user data from auth/user endpoint.

Better to use also $auth instance to set/modify $auth related stores, by this
https://auth.nuxtjs.org/api/storage/#local-storage
Just Incject app as You did with $axios in function attributes.

I'm already also using headers.token instead of response.

@devzom can you elaborate on how you configured that in the nuxt.config.js?