[Feature Request] Custom Callback

[cdiaz]

By default, if authentication fails, the AuthGuard will respond with a generic unauthorized error message.

But In some cases the built-in options are not sufficient to handle an authentication request.
Then it should be possible provide a Custom Callback to allow the application to handle success or failure.
For example:

const CustomCallback = (err, user, info) => {
  let message
  if (err) {
    return Promise.reject(err || new UnauthorizedException());
  } else if (typeof info != 'undefined' || !user) {
    switch (info.message) {
      case 'No auth token':
      case 'invalid signature':
      case 'jwt malformed':
      case 'invalid token':
        message = "You must provide a valid authenticated access token"
        break
      case 'jwt expired':
        message = "Your session has expired. Please log in again"
        break
    }
    return Promise.reject(new UnauthorizedException(message))
  }
  Promise.resolve(user);
}

  @Get('data')
  @UseGuards(AuthGuard('jwt', { session: false }, CustomCallback))
  getSensitiveData() {
    // this route is restricted
  }

[kamilmysliwiec]

Fixed in v1.0.5
Example:

@Get('data')
@UseGuards(AuthGuard('jwt', { session: false, callback }))
getSensitiveData() {
   // this route is restricted
}

when the callback looks like below:

const callback = (err, user, info) => {
   if (err || !user) {
      throw err || new UnauthorizedException();
   }
   return user;
}