auth-module: Nuxt Auth redirects (login/logout/home) not working

To be honest… that issue led me to abandon vue / nuxt totally !! Took me few hours to write a proper bug report… weeks and nothing ?

On simple things like that not working and no signs that it’ll be fixed…

when using passport js is just so simple… out of nuxt

I moved to Angular …

good luck guys

Now it’s my personal opinion and advice for new arrivers to nuxt… move on to angular, you’ll save your time, your nerves and your energy… At the end of the day, we are all free to do what we want, but I wish I had read somewhere the advice I’m giving here, it would have saved me several month of useless work/energy.

Edit: And yes sorry, I should mention nuxt can become a nice frontend to wordpress… but this is not how I picture the futur of my work. I’ve had to dive into wordpress code and I hope never to have to do it ever again.

@cantoute Your comment is very dangerous, you are selecting and encouraging a technology, it is based on your inexperience or frustration.

If you come from Wordpress, the thought of installing and using is hurting you and if you say that you did it faster in Angular, it is because capable your previous way of working adapted to that, and I understand the frustration you have hate towards a technology, but one knows that it has matured when it leaves that hatred back and returns to keep learning.

About your issue:

• In the code of middleware, callback always is public: https://github.com/nuxt-community/auth-module/blob/dev/lib/core/middleware.js#L30

• Maybe the bug of redirect (login, app, logout) was exist and was fixed, because for me in this time, work perfect! https://codesandbox.io/s/codesandbox-nuxt-nwzyp

Guys, this is most likely because your user routes are not defined correctly. Auth does not work if user object is not fetched correctly. If you don’t need user object, you have to set user route to false.

And you, mister Angular, in your codesandbox I don’t see any routes defined.

Came here to find a way to redirect my users only to find angular spam. @cantoute we get it, you moved to angular. Then go ahead and move on and please let us focus on the issue of the redirect here 👍

To the issue: I’m trying to make this happen with the auth0 strategy. No luck so far but will try some more suggestions from this thread and report back

how is anybody suppose to guess such a trick ?

And altho it’s not a nuxt issue, it’s common in all the nuxt eco-system.

I got more done by 3rd day working with angular than after 3 month fighting with nuxt…

It’s just an advice I gave you… If you want to waist energy on hacking a framework to get it to do such an exotic thing as using auth 😕

But for anyone reading here… lets not lead them into heal.

To be honest, nuxt has some nice sides, but don’t believe one second it’s easier than angular. And if you need auth in your app, using nuxt, be prepared to go threw hell… unless you don’t care auth feeling very bugus. At some point, who cares, if you rely on api auth to handle the real security, it’s just the interface that will behave bugus. Then one can hack it to feel better, and what happens when nuxt will overcome thos issue, need to unhack it? In a few years, it’ll be fun to remember what the story was…

Le 6 févr. 2020 à 12:19, Marko Bolliger notifications@github.com a écrit :

woa dude alm down its not an nuxt issue…

I fixed it like

redirect: { home: false }, and then in my login method

await this.$auth.loginWith(‘local’, { data: this.login }) this.$router.push(this.localePath({ name: ‘dashboard’ })) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437?email_source=notifications&email_token=AA7DNJLL6K6ACVYT4Q7HISLRBQS7FA5CNFSM4IR2HXA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK7S2JY#issuecomment-582954279, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJNVCT74SBI74VOOTVDRBQS7FANCNFSM4IR2HXAQ.

Thanks for all helps. Closing as there are enough answers to the original question. Let’s keep nuxt community a friendly place ❤️

v5 branch is also under heavy development and improvements including a more stable loggedIn state (#620) and many more improvements by @JoaoPedroAS51.

Please open a new issue with proper reporo in case you had similar issues 😃

I don’t think so… I get things done 10x faster since I’ve moved on… tired of waisting my time to do basic simple things that turns out a nightmare most of the time. Angular was much easier to get my hands on !!

Edit: why put thumbs down ?!!! It’s the truth, the learning curve to Angular is much easier than the one to broken logic in nuxt…

I had this behavior in my app and in my case the reason was something you also have in your sandbox in login.vue, line 44 — auth: false. Removing this line fixed the behavior for me (even though I have auth set up as app-wide middleware, the login route stays accessible). I kinda wish the docs were clearer.

cool 😃 just it took so long I gave up… And I continue following this thread as solving this will help many avoiding same disaster I had to go threw. And perhaps when this is solved I’ll consider using nuxt on other projects 😃 … Le 3 mai 2020 à 09:11, Fyroman @.***> a écrit : Guys, this is most likely because your user routes are not defined correctly. Auth does not work if user object is not fetched correctly. If you don’t need user object, you have to set user route to false. And you, mister Angular, in your codesandbox I don’t see any routes defined. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#437 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJILDHZRMW6RLCPL6T3RPVUO5ANCNFSM4IR2HXAQ.

🤔 I made a video and all was correct, nobody make a comment about my video 😥

Maybe it is late according to the previous comments but I had some problems with the logout redirect too. I was able to redirect and avoid this problem calling the auth logout method directly in one of my store actions:

async logout () { await this.$auth.logout() }

https://auth.nuxtjs.org/api/auth.html#logout-args

Please, don’t fight, If this report don’t help to fix the bug or the reporters don’t want to help to fix, I recommend close, maybe another people create new report with more info or with more expectations in helping.

So after spending many hours on this, I figured this out:

• If you are using axios baseURL and mode ‘universal’ in nuxt config, then redirects won’t work. Change mode to ‘spa’.
• OR, stop using axios baseURL and use nuxt axios proxy instead.

Either solution should resolve redirection issues.

But as I said earlier… 4h after switching to Angular I had all this working like a charm… and was further in my app then in 1 week with nuxt…

But it was annoying that when login failed it would request user anyway (My login endpoint is return always 200 with login status in JSON reponse)

Hi @mtangoo! I believe one solution would be creating a custom scheme that extends local scheme. That way you can override the login method to match your requirements and enable autoFetchUser again 😃

Before creating the custom scheme, you will need to add @nuxtjs/auth to transpile.

nuxt.config.js

build: {
  transpile: ['@nuxtjs/auth']
}

With this set up, you can create your scheme file.

~/schemes/customLocalScheme.js

import LocalScheme from '@nuxtjs/auth/lib/schemes/local'

export default class CustomLocalScheme extends LocalScheme {
  // Override `login` method of `local` scheme
  async login (endpoint) {
    if (!this.options.endpoints.login) {
      return
    }

    // Ditch any leftover local tokens before attempting to log in
    await this.$auth.reset()

    const { response, result } = await this.$auth.request(
      endpoint,
      this.options.endpoints.login,
      true
    )

    // If not succeeded, bail
    if (!response.data.success) {
      return
    }

    // Set token if `tokenRequired` is enabled
    if (this.options.tokenRequired) {
      const token = this.options.tokenType
        ? this.options.tokenType + ' ' + result
        : result

      this.$auth.setToken(this.name, token)
      this._setToken(token)
    }

    // Fetch user if `autoFetchUser` is enabled
    if (this.options.autoFetchUser) {
      await this.fetchUser()
    }

    return response
  }
}

Then set your new scheme in the auth config.

nuxt.config.js

auth: {
  strategies: {
    local: {
      _scheme: '~/schemes/customLocalScheme',
      /* ... */
    }
  }
}

This is not report of a Bug! The Nuxt Auth is the Bug! for me The Nuxt Auth takes more than 3 times of completing all other part of my project. Auth documentation seems complete but it is not strait-forward telling.

I don’t think so… I get things done 10x faster since I’ve moved on… tired of waisting my time to do basic simple things that turns out a nightmare most of the time. Angular was much easier to get my hands on !!

Came here to find a way to redirect my users only to find angular spam. @cantoute we get it, you moved to angular. Then go ahead and move on and please let us focus on the issue of the redirect here 👍

To the issue: I’m trying to make this happen with the auth0 strategy. No luck so far but will try some more suggestions from this thread and report back

I could simply delete that bug report and send you all to f…k yourself… 6 month and no-one f…ing bothered to think of trying to solve it… no-one needs auth in their app ?

Watch it guys… next comment like this and I delete that bug report and you can do it yourself to see !!

And you want to make me look like I’m the bad guy here when it seems here that I’m the only-one here who actually did something looking towards trying to solve the problem ?!! Yeah, making a bug report is part of looking into the right direction… And because it came obvious that this isn’t the common behavior here, yes, I advertise for anyone not yet in that trap to look elsewhere. If it feels to you guy like a kick in the b…ks, it’s what it is!! It’s my f…k you very much for the time I wasted with this crap… your crap?

Sorry to be rude but to some point one collect what one deserves !! And that community just reminds me of that of wordpress !!

Nice job to have figured this out.

But how about ditching all that crap and just have something like nuxt-community/passport

It could be more useful… and probably a complet rewrite could give it a chance to get somewhere useable a bit further than just to get “what I need write now to work, the rest we’ll see later”… Isn’t it wordpress world philosophy?

How many dev contributing to nuxt are actually in search of a wordprout alternative?

It’s impossible to think out of the box from within the box…

I think working with angular could open the box for many nuxt dev… It’s what happened to me, and since, each time I have to deal with nuxt, it just reminds me of wordpress…

I think you made a good analysis of the problem, so you have to be pretty smart to have worked this out and perhaps your time is too precious to continue bother with nuxt 😃

Regards

Le 6 févr. 2020 à 02:50, jasonlyu123 notifications@github.com a écrit :

https://github.com/nuxt-community/auth-module/blob/85466345311bf882ae2f603ba43ef1dc638d2cdb/lib/core/auth.js#L58 https://github.com/nuxt-community/auth-module/blob/85466345311bf882ae2f603ba43ef1dc638d2cdb/lib/core/auth.js#L58 The problem is with this line. It check whether current page enable auth middleware to see has right to stay on current page when logout. But I can’t figure out the point of this check when login.

When I remove auth: false, or use auth: ‘guest’ the redirect works.

https://auth.nuxtjs.org/api/options.html#redirect https://auth.nuxtjs.org/api/options.html#redirect The problem origin post encounter is actually specified in the docs. you’ll only be redirect when

after logout, current route is protected.

Maybe it could be an option to disable this behavior.

The problem when login, on the other hand, is weird. It make sense to think you would have to disable auth middleware to prevent infinite redirect on login page. But you actually don’t have to do that. When you disable it, it’ll prevent the redirect. It not a straightforward behavior.

Can any person of the core team explain why this check is necessary while login or it’s a bug?

If the check is necessary, maybe add a note to the docs about you can’t disable auth middleware in login page. If it’s a bug. How to fix it is a problem, just disable the check in login would result in different redirect page if the fallback redirect dev added after login is different.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437?email_source=notifications&email_token=AA7DNJLC6SL46D3FDNKB7ULRBOQKVA5CNFSM4IR2HXA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK6ASBI#issuecomment-582748421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJJRB73GHJ6ST22YH23RBOQKVANCNFSM4IR2HXAQ.

I will try that one. Makes life easy sharing with projects

@cantoute @mjzarrin @la-jamesh

I made this video to test the module and see all normal. If your have some config to test or fix, send me here or in private @MrJmpl3 in Twitter, to made another video

https://www.youtube.com/watch?v=uYZBoCDMZ4I&feature=youtu.be

@DavidFeller modified my comment to be more clear, is that helpful?

Le 31 mars 2020 à 23:45, Jose Manuel Casani Guerra notifications@github.com a écrit :

@cantoute https://github.com/cantoute If you ask about the callback page for auth users, the callback page if always public:

https://github.com/nuxt-community/auth-module/blob/dev/lib/core/middleware.js#L54 https://github.com/nuxt-community/auth-module/blob/dev/lib/core/middleware.js#L54

I’m really sorry guys, this is over 6 month old and I did fight over 2 weeks on trying to get this to work, reading loads of contradictory information…

All this is over complicated and twisted minded when compared to using passport strategy (over vanilla js or with other frameworks)

To me, all this nuxt-auth is to be refactored from base and I’m not going to put my head into this ever again.

Perhaps nuxt dev should work with other framework and consider a total refactor of a new vuejs universal assembly with a wider view of the problem… a next-vue ?

My advise to anyone here is to not waist more energy on this sinking ship… But every one is free to spend it’s time on what ones want, even if it’s on a sinking ship…

I can only wish you all the best, and really I can’t get it that I’m the only one having issue with nuxt-auth… uness one doesn’t care having to super-hack to get a simple auth to work. Really, give a try to any passport auth package to see how simple it is to have something powerful to work… it’s really less then 10 lines clear and simple!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437#issuecomment-607010622, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJPFFDLGP4QWCIZJ7N3RKK2FNANCNFSM4IR2HXAQ.

Le 31 mars 2020 à 11:59, Sumit Kumar notifications@github.com a écrit :

Came here to find a way to redirect my users only to find angular spam. @cantoute https://github.com/cantoute we get it, you moved to angular. Then go ahead and move on and please let us focus on the issue of the redirect here 👍

6 month still not one step towards a solution…

My advice isn’t spam… it’s just a warning to anyone not to get trapped in this loophole of asking something so exotic for an app to be able to manage authentification.

Perhaps you can read between the lines my frustration (and the fact I can’t bare mediocrity) I had worked on an app assuming nuxt could manage a simple authentification… lost 3 month of my time for that mistake, so my honest advice to anyone wanting to use nuxt is that I hope you don’t need authentification.

Took me several hours to do this bug report not because no-one hit into this issue, but because no-one else bothered… And they were right, no-one look at it for over 3 month and still not a single hope of this issue to get near by to be solved simply because this auth module doesn’t make any sense… why not simply have passport integration ? (ex: nuxt/auth-passport)

having a universal framework not having a single usable auth solution is a crazy… but this isn’t the worse part of the incoherence in this framework, it seems so much that dev here are ex-wordpress dev repeating exactly what they where trying to run away from…

To the issue: I’m trying to make this happen with the auth0 strategy. No luck so far but will try some more suggestions from this thread and report back

Enjoy…

issue published 6 month ago… the only clue shoing up is that could be Vue.js devtools chrome extension could be related to the issue… 😕

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437#issuecomment-606718801, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJKYDQW2XHGNAHWG4O3RKIHNXANCNFSM4IR2HXAQ.

I have same problem. Make sure user endpoint gets the user object correctly. If your user api responds the whole user object set the propertyName to false to tell Nuxt to directly use API response.

auth: {
    strategies: {
      local: {
        endpoints: {
          login: { url: '/api/auth/local', method: 'post', propertyName: 'jwt' },
          logout: { url: '/api/auth/logout', method: 'post' },
          user: { url: '/api/users/me', method: 'get', propertyName: false }
        }
      }
    }
  }

woa dude alm down its not an nuxt issue…

I fixed it like

redirect: {
      home: false
    },

and then in my login method

  await this.$auth.loginWith('local', {
          data: this.login
        })
        this.$router.push(this.localePath({ name: 'dashboard' }))

its not 100% working maybe you can add check on mounted/created and redirect

I’ve been struggling the same problem and after taking a look into the source of auth-module I have figure out the configuration and it works, you can take a look here https://codesandbox.io/s/nuxt-starter-n4b6v-n4b6v Note that in login page I have auth: “guest”

I get 'this page could not be found` This shit is annoying

Create the page that is not found, under /pages directory. If you need any help. just reply!

I get 'this page could not be found`

This shit is annoying

Hi,

I found out it is due to nuxt-i18n - it creates routes for all the different languages(locales) and the auth module does’nt, out of the box, play nicely.

What i did on ‘nuxt-i18n’ was to disable the prefix option via strategy: 'no_prefix'

However, im having issues with the module as it continually says the local strategy is not defined

  /*
   ** Nuxt.js modules
   */
  modules: [
    // Doc: https://axios.nuxtjs.org/usage
    '@nuxtjs/axios',
    '@nuxtjs/pwa',
    '@nuxtjs/auth-next',


    [
      'nuxt-i18n',
      {
        lazy: true,
        locales: [
          {
            code: 'en',
            file: 'en.js'
          }
        ],
        strategy: 'no_prefix',
        defaultLocale: 'en',
        fallbackLocale: 'en',
        lazy: true,
        langDir: 'locales/'
      }
    ]
  ],

 /*
   ** Auth module configuration
   ** See https://auth.nuxtjs.org/#
   */
  auth: {
    strategies: {
      local: {
        endpoints: {
          login: { url: 'auth/login', method: 'post' },
          user: false,
          logout: { url: 'auth/logout', method: 'get' }
        },

        tokenRequired: true,
        autoFetchUser: false
        //   tokenType: false
      }
    }
  },

Ive been trying to play with the options to try and get it to work and have had no luck.

I had a similar problem. I had to redirect the user depending on the Role (User or admin), so, the solution of just writing one common redirection did not work for me. I did the following, I have created a vue page called redirect.vue and there I wrote a middleware that checks the role of the user in order to redirect to the correct page (getting the users info from the vuex store), this solution may not be the best one but works. I hope this help someone!

redirect.vue (page):

<template>
  <div></div>
</template>

<script>
export default {
  middleware: 'redirect_middleware',
  data() {
    return {}
  }
}
</script>

redirect_middleware.js (middleware)

export default function({ store, redirect }) {
  if (
    store.state.auth.loggedIn &&
    (store.state.auth.user.role === 'user'
  ) {
    return redirect('/userspage')
  } else if (
    store.state.auth.loggedIn &&
    store.state.auth.user.role === 'admin'
  ) {
    return redirect('/adminpage')
  }
}

Note: For this to work, make sure that in the users table is a field called “role”

auth object inside nuxt.config.js

auth: {
  strategies: {
    local: {
      endpoints: {
        login: {
          url: 'api/auth/login',
          method: 'post',
          propertyName: 'token'
        },
        logout: {
          url: 'api/auth/logout',
          method: 'get'
        },
        user: {
          url: 'api/me',
          method: 'get',
          propertyName: 'data'
        }
      }
    }
  },
  redirect: {
    home: '/auth/redirect',
    login: '/auth/login',
    logout: '/'
  },
  fullPathRedirect: true
}

From Colombia to the world! 😃

https://github.com/nuxt-community/auth-module/blob/85466345311bf882ae2f603ba43ef1dc638d2cdb/lib/core/auth.js#L58

The problem is with this line. It check whether current page enable auth middleware to see if you have right to stay on current page when logout. But I can’t figure out the point of this check when login.

When I remove auth: false, or use auth: 'guest' the redirect works.

https://auth.nuxtjs.org/api/options.html#redirect The problem origin post encounter is actually specified in the docs. you’ll only be redirect when

after logout, current route is protected.

Maybe it could be an option to disable this behavior.

The problem when login, on the other hand, is weird. It make sense to think you would have to disable auth middleware to prevent infinite redirect on login page. But you actually don’t have to do that. When you disable it, it’ll prevent the redirect. It not a straightforward behavior.

Can any person of the core team explain why this check is necessary while login or it’s a bug?

If the check is necessary, maybe add a note to the docs about you can’t disable auth middleware in login page. If it’s a bug. How to fix it is a problem, just disable the check in login would result in different redirect page if the fallback redirect dev added after login is different.

Also, I want to note that the “auth” option must be used on layouts, not on pages ( I was doing it wrong ) for this to work. Maybe they don’t need to fix the module, but update the docs ( because they are confusing )

For those who like me got stuck on why their own redirection was going through home page even with the home: false

await this.$auth.loginWith("local", { data: { email, password } })
// i get a specific URL to redirect to from my user response
const url = this.$auth.user.url
this.$router.push(`/${url}`)

Switching to logout: false instead made the job (makes no sense but it’s working for now).

My auth config :

auth: {
	redirect: {
		login: "/login",
		logout: false
	},
	strategies: {
		local: {
			endpoints: {
				login: {
					url: "/users/login/token",
					method: "post",
					propertyName: "token"
				},
				user: { url: "/users/login/me", method: "get", propertyName: "user" },
		                logout: { url: "/api/auth/logout", method: "post" },
			}
		}
	}
}

for me all suggestion didn’t work. The login was succeeding, everything set to local storage but no redirection to the correct page. Checked all I could and didn’t work. Then I remembered one other project I worked with nuxt and found the solution and here I share it

my backend was sending back something like

{
    "success" : true,
    "message" : "Succesfully logged in",
    "token" : "JWT Token Here"
}

    async login () {
      try {
        const response = await this.$auth.loginWith('local', {
          data: {
            username: this.username,
            password: this.password
          }
        })
        if (response.data.success === true) {
          this.$auth.setUserToken(response.data.token)
        }
      } catch (err) {
        console.log(err)
      }
    }

revisiting this it looks like I’m only having issues when deployed to AWS via serverless/fastify. Running locally through nuxt in universal mode with auth0 appears to be working fine. I’ll have to see where my configuration is wrong for serverless/fastify. Thanks for all the comments here.

This is not report of a Bug! The Nuxt Auth is the Bug! for me The Nuxt Auth takes more than 3 times of completing all other part of my project. Auth documentation seems complete but it is not strait-forward telling.

time to have a nuxt/auth-passort !!

So after spending many hours on this, I figured this out:

• If you are using axios baseURL and mode ‘universal’ in nuxt config, then redirects won’t work. Change mode to ‘spa’.
• OR, stop using axios baseURL and use nuxt axios proxy instead.

Either solution should resolve redirection issues.

Great work !

Thank you very much for all of us to have isolated the issue.

I would never have guessed the issue could come from combining with axios 😕

With that clue perhaps someone will find a fix… but I would’t count on any of those who down voted me here lol (I have doubt on their ability to code… Could they prove me wrong, I would apologize, but I would be really surprised, when coders make me look like the bad guy, by my experience, they had proven they were trying to hide their incompetence. Please prove me wrong 😃

Le 1 avr. 2020 à 00:19, Jose Manuel Casani Guerra notifications@github.com a écrit :

Le 1 avr. 2020 à 00:15, Jose Manuel Casani Guerra @.***> a écrit : Well, can explain specifically the bug? I think make a video trying to reproduce the bug and fix. I still don’t understand what in the sandbox isn’t clear about nothing working as expected… nor a “auth only” page nor login that should route to app nor logout to home… … x-msg://57/# — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#437 (comment) https://github.com/nuxt-community/auth-module/issues/437#issuecomment-607020128>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJK7TSJ7PYTPBPXMOVDRKK5XLANCNFSM4IR2HXAQ https://github.com/notifications/unsubscribe-auth/AA7DNJK7TSJ7PYTPBPXMOVDRKK5XLANCNFSM4IR2HXAQ.

Ok, I will make the video trying to reproduce the bug and share here.

If you like.

I don’t see how this will improve the situation but it can’t heart.

perhaps one could look into integrating passport

when looking at this it really looks painful to get them working together! https://github.com/Scharkee/vue-nuxt-passport-bulma-express-boiler https://github.com/Scharkee/vue-nuxt-passport-bulma-express-boiler

and see of a way to make passport easier to integrate… a @nuxt/auth-passport ?

just an idea…

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437#issuecomment-607021276, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJOGEEOGNXX532BRYELRKK6GVANCNFSM4IR2HXAQ.

Le 1 avr. 2020 à 00:15, Jose Manuel Casani Guerra notifications@github.com a écrit :

Well, can explain specifically the bug? I think make a video trying to reproduce the bug and fix.

I still don’t understand what in the sandbox isn’t clear about nothing working as expected… nor a “auth only” page nor login that should route to app nor logout to home…

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437#issuecomment-607020128, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJK7TSJ7PYTPBPXMOVDRKK5XLANCNFSM4IR2HXAQ.

Le 31 mars 2020 à 23:38, Jose Manuel Casani Guerra notifications@github.com a écrit :

Le 31 mars 2020 à 23:32, Jose Manuel Casani Guerra @.***> a écrit : @cantoute https://github.com/cantoute https://github.com/cantoute https://github.com/cantoute I wish start again, can you try with this example, and explain specifically the bug. https://nwzyp.sse.codesandbox.io/ https://nwzyp.sse.codesandbox.io/ https://nwzyp.sse.codesandbox.io/ https://nwzyp.sse.codesandbox.io/ I don’t see what isn’t clear here… When I click on (try me before login to see…) I get to see a page that should require auth… amongst other things that don’t behave as expected … x-msg://42/# — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#437 (comment) https://github.com/nuxt-community/auth-module/issues/437#issuecomment-607007110>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJJV2RA5TRFW22ZDBE3RKKYUHANCNFSM4IR2HXAQ https://github.com/notifications/unsubscribe-auth/AA7DNJJV2RA5TRFW22ZDBE3RKKYUHANCNFSM4IR2HXAQ.

That is because I use my API, change with your api and try. I can’t reproduce the bug.

Strange…

In the sandbox I put with bug report I still have the issue

https://codesandbox.io/s/codesandbox-nuxt-0vhpu https://codesandbox.io/s/codesandbox-nuxt-0vhpu

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437#issuecomment-607008868, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJI3IKY34QVA6WKF2K3RKKZNBANCNFSM4IR2HXAQ.

Le 31 mars 2020 à 12:23, Majid Zarrin notifications@github.com a écrit :

Vue.js devtools chrome extension!!! removing it from chrome made my Nuxt app alive.

Vue.js devtools chrome extension https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd/related?hl=en

Marvelous !!

First answer that looks into solving that issue…

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nuxt-community/auth-module/issues/437#issuecomment-606732184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7DNJKI53OVPWBHH6UHRXTRKIKITANCNFSM4IR2HXAQ.

https://github.com/nuxt-community/auth-module/blob/85466345311bf882ae2f603ba43ef1dc638d2cdb/lib/core/auth.js#L58

The problem is with this line. It check whether current page enable auth middleware to see if you have right to stay on current page when logout. But I can’t figure out the point of this check when login.

When I remove auth: false, or use auth: 'guest' the redirect works.

https://auth.nuxtjs.org/api/options.html#redirect The problem origin post encounter is actually specified in the docs. you’ll only be redirect when

after logout, current route is protected.

Maybe it could be an option to disable this behavior.

The problem when login, on the other hand, is weird. It make sense to think you would have to disable auth middleware to prevent infinite redirect on login page. But you actually don’t have to do that. When you disable it, it’ll prevent the redirect. It not a straightforward behavior.

Can any person of the core team explain why this check is necessary while login or it’s a bug?

If the check is necessary, maybe add a note to the docs about you can’t disable auth middleware in login page. If it’s a bug. How to fix it is a problem, just disable the check in login would result in different redirect page if the fallback redirect dev added after login is different.

I kinda wish the docs were clearer.

When I looked at the doc back then, it said that you had to specify auth: false; But what doc are we talking about as there are 2 docs for this module that contredicts one another.

thanks vakrolme

but this doesn’t fix the problem of letting access to pages that shouldn’t let you in as wen one clicks on “Callback (try me before login to see…)”