Is there a way to disable pages altogether?

[jakiestfu]

Question 💬

I've built my own UI for handling sessions altogether, so I'd like to disable the automatically generated pages.

I've tried adding the following to no avail. I'm using the email and github providers.

...
   pages: {
      signIn: null,
      signOut: null,
      error: null,
      verifyRequest: null,
      newUser: null,
    },
...

How to reproduce ☕️

Unable to reproduce my desired behavior.

Contributing 🙌🏽

No, I am afraid I cannot help regarding this

[Pruxis]

I would like to be able to disable these pages too.
I've already checked the source code and this seems to be pretty easy to add.

However what would be the desired approach for this @iaincollins ?

If we could discuss this then I'd be happy to open a PR to add this functionality, as we really dislike "non-owned" pages to be accessible to the end-user.

[phelanma]

(following the advise given here*)
Setting / for pages will result '?callbackUrl=http...' being appended to url; which is not really the desire? should it not just redirect without callback being appended?

[pingustar]

@phelanma did you find a solution to removing the appended callbackUrl query param?

[zekepari]

@pingustar Did you find a solution for this?

[chev0004]

@pingustar have you found a solution yet?

[fxbayuanggara]

You can add the provider id to signIn method, for example, signIn('keycloak')

[alihesari]

Did anyone find a solution to this?

I use Keycloak as a provider. Keycloak has a signin page but sometimes nextauthjs redirects users to this page. I want to disable this page and not redirect users to this page. The route of this page is api/auth/signin?csrf=true

[reslear]

any news? I would like to use only the api

[ericmesmo]

Did you find a way?

[reslear]

I decided not to migrate. I'm using passportjs.

[kr-yeon]

+1

[svarup]

+1