Docs custom sign in page: Note that `auth: false` needs to be set to avoid redirect loop about nuxt-auth HOT 7 CLOSED

As much as I would like this, I don't think that we should rip apart the NuxtAuthHandler config -> from that point onwards the advantage of having many guides, tutorials, ... from NextAuth that also apply to nuxt-auth vanishes.

If we could import from the server side from our client-code it may be something different. Our middleware could import the auth handler and try to read the configuration from it. But ofc. that's also super dangerous because the nuxt auth handler could also contain secrets.

from nuxt-auth.

As much as I would like this, I don't think that we should rip apart the NuxtAuthHandler config -> from that point onwards the advantage of having many guides, tutorials, ... from NextAuth that also apply to nuxt-auth vanishes.

Yeah, that's exactly my point.

from nuxt-auth.

Yeah, I also thought about having path matching with next-auth pages. But we can't import the auth options as they are defined by the user in [...].ts, so we would need to add the auth.pages to nuxt.config and merge them into NuxtAuthHandler.

from nuxt-auth.

So your idea is something like ignorePaths: ['/foo', '/bar'], right?

from nuxt-auth.

Yes, that's it! I haven't looked into it, but it would be nice to follow the same patterns that nitro uses for routeRules: https://nitro.unjs.io/config/#routerules

Maybe the naming can be publicPaths instead of ignorePaths? This naming would be more independent of the global-middleware context. Or maybe even better, restructure the global middleware settings to allow:

enableGlobalAppMiddleware: boolean | {
  enabled: boolean
  ignoresPaths: string[]
}

from nuxt-auth.

I've added this note to the new docs, see #90 and soon https://sidebase.io/nuxt-auth/application-side/custom-sign-in-page

I've moved my proposal to allow ignore Paths into #91.

Closing this via #90

from nuxt-auth.

This was added with #90

from nuxt-auth.