[Issue]: Redirect banned user to a custom page after login in with OAuth (Google)

Problem:
Here is what I'm getting after trying to login as a "banned" user using OAuth (Google).

http://localhost:3000/api/auth/error?error=banned&error_description=You%20have%20been%20banned%20from%20this%20application.%20Please%20contact%20support%20if%20you%20believe%20this%20is%20an%20error

Current workaround:

  hooks: {
    before: createAuthMiddleware(async (ctx) => {
      if (ctx.path === "/error") {
        if (ctx.query && "error" in ctx.query && ctx.query.error === "banned") {
          throw ctx.redirect(`/banned`);
        }
      }
    }),
  },

  hooks: {
    before: createAuthMiddleware(async (ctx) => {
      if (ctx.path === "/error") {
        if (ctx.query && "error" in ctx.query && ctx.query.error === "banned") {
          throw ctx.redirect(`/banned`);
        }
      }
    }),
  },

  hooks: {
    before: createAuthMiddleware(async (ctx) => {
      if (ctx.path === "/error") {
        if (ctx.query && "error" in ctx.query && ctx.query.error === "banned") {
          throw ctx.redirect(`/banned`);
        }
      }
    }),
  },

  hooks: {
    before: createAuthMiddleware(async (ctx) => {
      if (ctx.path === "/error") {
        if (ctx.query && "error" in ctx.query && ctx.query.error === "banned") {
          throw ctx.redirect(`/banned`);
        }
      }
    }),
  },

I'm on the latest version of better-auth (v1.2.10)
I found those issues to be related #1580 #1282

Those issues already exist I didn't want to open a new issue, but I need help with how to handle things correctly with the current version of better-auth.
I’d appreciate guidance on the proper way to handle this in v1.2.10, especially with user context preserved.

Limitations:

banned page doesn't have any context about banned user
if I want to show the banReason I can't.
if I want to show a countdown timer I can't

Request:
I'd appreciate taking another look at those issues mentioned above

GitHub

`errorCallbackURL` is not working it is ignored on error · Issue #...

Is this suited for github? #1581 To Reproduce most probably this is due to callback api route and in my case code is not generated as i cancel the process to choose another account logger do print ...

GitHub

Customize Ban user login response · Issue #1282 · better-auth/bet...

Is this suited for github? Yes, this is suited for github Is your feature request related to a problem? Please describe. I want to customize the response when a banned user tries to login. currentl...

Omar-7iooOP•6/29/25, 10:58 AM

This issue got solved on version 1.2.11 or 1.2.12

Karthickeyan•7/6/25, 5:36 AM

How did you manage to redirect user to banned page with ban reason and expires?

Omar-7iooOP•7/7/25, 4:21 PM

Sadly I couldn't
The issue is you don't have the session for the user. Currently I have no clue how I would do this

Omar-7iooOP•7/7/25, 4:23 PM

But for what I experienced using better-auth ban reason and expiry is not meant for showing a page, but an popup on login.
So when the user tries to login in he will get an error and you could customize this error since you know that user and can get ban reason and ban expiry

LightTab2•7/7/25, 7:55 PM

const { error } = await auth.signIn.email(
{
    email:    email,
    password: password
}, {});
if (error?.code === "BANNED_USER")
{
    const { banReason, expiryTime } = getBanInfo(email);
    navigate({ to: '/banned', search: 
        { banReason: banReason, expiryTime: expiryTime } });
}

const { error } = await auth.signIn.email(
{
    email:    email,
    password: password
}, {});
if (error?.code === "BANNED_USER")
{
    const { banReason, expiryTime } = getBanInfo(email);
    navigate({ to: '/banned', search: 
        { banReason: banReason, expiryTime: expiryTime } });
}

LightTab2•7/7/25, 7:55 PM

LightTab2•7/7/25, 7:57 PM

The query to the database should be something like that

select "banReason", "banExpires" from "user" where email = $1;

select "banReason", "banExpires" from "user" where email = $1;

LightTab2•7/7/25, 8:04 PM

Oh nvm, it's OAuth...

LLightTab2 ||```js const { error } = await auth.signIn.email( { email: email, pa...

Omar-7iooOP•7/7/25, 10:14 PM

If I'm not wrong this won't work in the latest version 1.12.121.12.12 unless you do the workaround mentioned in initial message.
See https://github.com/better-auth/better-auth/pull/2640#ref-commit-ca260a3

GitHub

Use custom errorURL when available by ErikPetersenDev · Pull Reque...

This PR resolves: #2519
Summary
There are a few places in the code where the custom errorURL is not checked/used, resulting in the default Better Auth error page. This PR copies the way this is do...

LLightTab2 Oh nvm, it's OAuth...

Omar-7iooOP•7/7/25, 10:20 PM

If the errorCallback was working you could do something like:
errorCallback: "/login?userId=..." // better-auth will pass the error paramerrorCallback: "/login?userId=..." // better-auth will pass the error param
Then you can set a useEffect to check if the error param exists, if yes check the code and fetch the ban reason and expiry by userId

OOmar-7ioo If I'm not wrong this won't work in the latest version `1.12.12` unless you do t...

LightTab2•7/8/25, 8:26 AM

I just checked, this still works but only for email signin, OAuth is problematic

OOmar-7ioo If the errorCallback was working you could do something like: `errorCallback: "...

LightTab2•7/8/25, 8:34 AM

I have no idea how to extract userID from a Google login

LightTab2•7/8/25, 10:22 AM

I did some reverse engineering and it seems impossible without consuming the token and breaking callback/:idcallback/:id route, so probably the only realistic way is patching the library

The surreal way to do it is redefinining entire callback/:idcallback/:id route in a hook, basicaly copy pasting its code with your changes, but this doesn't work well, because it uses some not exported functions, which you'd need to copy paste as well...

[Issue]: Redirect banned user to a custom page after login in with OAuth (Google)

Similar Threads

Similar Threads

Similar Threads