主頁 > 知識(shí)庫 > redis 實(shí)現(xiàn)登陸次數(shù)限制的思路詳解

redis 實(shí)現(xiàn)登陸次數(shù)限制的思路詳解

熱門標(biāo)簽:高碑店市地圖標(biāo)注app 南京手機(jī)外呼系統(tǒng)廠家 400電話辦理的口碑 b2b外呼系統(tǒng) 廊坊外呼系統(tǒng)在哪買 地圖標(biāo)注工廠入駐 四川穩(wěn)定外呼系統(tǒng)軟件 一個(gè)地圖標(biāo)注多少錢 臺(tái)灣電銷

title: redis-login-limitation 

利用 redis 實(shí)現(xiàn)登陸次數(shù)限制, 注解 + aop, 核心代碼很簡(jiǎn)單.

基本思路

比如希望達(dá)到的要求是這樣: 在 1min 內(nèi)登陸異常次數(shù)達(dá)到5次, 鎖定該用戶 1h

那么登陸請(qǐng)求的參數(shù)中, 會(huì)有一個(gè)參數(shù)唯一標(biāo)識(shí)一個(gè) user, 比如 郵箱/手機(jī)號(hào)/userName

用這個(gè)參數(shù)作為key存入redis, 對(duì)應(yīng)的value為登陸錯(cuò)誤的次數(shù), string 類型, 并設(shè)置過期時(shí)間為 1min. 當(dāng)獲取到的 value == "4" , 說明當(dāng)前請(qǐng)求為第 5 次登陸異常, 鎖定.

所謂的鎖定, 就是將對(duì)應(yīng)的value設(shè)置為某個(gè)標(biāo)識(shí)符, 比如"lock", 并設(shè)置過期時(shí)間為 1h

核心代碼

定義一個(gè)注解, 用來標(biāo)識(shí)需要登陸次數(shù)校驗(yàn)的方法

package io.github.xiaoyureed.redispractice.anno;
import java.lang.annotation.*;
@Documented
@Target({ElementType.METHOD})
@Retention(RetentionPolicy.RUNTIME)
public @interface RedisLimit {
  /**
   * 標(biāo)識(shí)參數(shù)名, 必須是請(qǐng)求參數(shù)中的一個(gè)
   */
  String identifier();
  /**
   * 在多長時(shí)間內(nèi)監(jiān)控, 如希望在 60s 內(nèi)嘗試
   * 次數(shù)限制為5次, 那么 watch=60; unit: s
   */
  long watch();
  /**
   * 鎖定時(shí)長, unit: s
   */
  long lock();
  /**
   * 錯(cuò)誤的嘗試次數(shù)
   */
  int times();
}

編寫切面, 在目標(biāo)方法前后進(jìn)行校驗(yàn), 處理...

package io.github.xiaoyureed.redispractice.aop;
@Component
@Aspect
// Ensure that current advice is outer compared with ControllerAOP
// so we can handling login limitation Exception in this aop advice.
//@Order(9)
@Slf4j
public class RedisLimitAOP {
  @Autowired
  private StringRedisTemplate stringRedisTemplate;
  @Around("@annotation(io.github.xiaoyureed.redispractice.anno.RedisLimit)")
  public Object handleLimit(ProceedingJoinPoint joinPoint) {
    MethodSignature methodSignature = (MethodSignature) joinPoint.getSignature();
    final Method   method     = methodSignature.getMethod();
    final RedisLimit redisLimitAnno = method.getAnnotation(RedisLimit.class);// 貌似可以直接在方法參數(shù)中注入 todo
    final String identifier = redisLimitAnno.identifier();
    final long  watch   = redisLimitAnno.watch();
    final int  times   = redisLimitAnno.times();
    final long  lock    = redisLimitAnno.lock();
    // final ServletRequestAttributes att       = (ServletRequestAttributes) RequestContextHolder.currentRequestAttributes();
    // final HttpServletRequest    request     = att.getRequest();
    // final String          identifierValue = request.getParameter(identifier);
    String identifierValue = null;
    try {
      final Object arg      = joinPoint.getArgs()[0];
      final Field declaredField = arg.getClass().getDeclaredField(identifier);
      declaredField.setAccessible(true);
      identifierValue = (String) declaredField.get(arg);
    } catch (NoSuchFieldException e) {
      log.error(">>> invalid identifier [{}], cannot find this field in request params", identifier);
    } catch (IllegalAccessException e) {
      e.printStackTrace();
    }
    if (StringUtils.isBlank(identifierValue)) {
      log.error(">>> the value of RedisLimit.identifier cannot be blank, invalid identifier: {}", identifier);
    }
    // check User locked
    final ValueOperationsString, String> ssOps = stringRedisTemplate.opsForValue();
    final String             flag = ssOps.get(identifierValue);
    if (flag != null  "lock".contentEquals(flag)) {
      final BaseResp result = new BaseResp();
      result.setErrMsg("user locked");
      result.setCode("1");
      return new ResponseEntity>(result, HttpStatus.OK);
    }
    ResponseEntity result;
    try {
      result = (ResponseEntity) joinPoint.proceed();
    } catch (Throwable e) {
      result = handleLoginException(e, identifierValue, watch, times, lock);
    }
    return result;
  }
  private ResponseEntity handleLoginException(Throwable e, String identifierValue, long watch, int times, long lock) {
    final BaseResp result = new BaseResp();
    result.setCode("1");
    if (e instanceof LoginException) {
      log.info(">>> handle login exception...");
      final ValueOperationsString, String> ssOps = stringRedisTemplate.opsForValue();
      Boolean                exist = stringRedisTemplate.hasKey(identifierValue);
      // key doesn't exist, so it is the first login failure
      if (exist == null || !exist) {
        ssOps.set(identifierValue, "1", watch, TimeUnit.SECONDS);
        result.setErrMsg(e.getMessage());
        return new ResponseEntity>(result, HttpStatus.OK);
      }
      String count = ssOps.get(identifierValue);
      // has been reached the limitation
      if (Integer.parseInt(count) + 1 == times) {
        log.info(">>> [{}] has been reached the limitation and will be locked for {}s", identifierValue, lock);
        ssOps.set(identifierValue, "lock", lock, TimeUnit.SECONDS);
        result.setErrMsg("user locked");
        return new ResponseEntity>(result, HttpStatus.OK);
      }
      ssOps.increment(identifierValue);
      result.setErrMsg(e.getMessage() + "; you have try " + ssOps.get(identifierValue) + "times.");
    }
    log.error(">>> RedisLimitAOP cannot handle {}", e.getClass().getName());
    return new ResponseEntity>(result, HttpStatus.OK);
  }
}

這樣使用:

package io.github.xiaoyureed.redispractice.web;
@RestController
public class SessionResources {
  @Autowired
  private SessionService sessionService;
  /**
   * 1 min 之內(nèi)嘗試超過5次, 鎖定 user 1h
   */
  @RedisLimit(identifier = "name", watch = 30, times = 5, lock = 10)
  @RequestMapping(value = "/session", method = RequestMethod.POST)
  public ResponseEntityLoginResp> login(@Validated @RequestBody LoginReq req) {
    return new ResponseEntity>(sessionService.login(req), HttpStatus.OK);
  }
}

references

https://github.com/xiaoyureed/redis-login-limitation

總結(jié)

以上所述是小編給大家介紹的redis 實(shí)現(xiàn)登陸次數(shù)限制的思路詳解,希望對(duì)大家有所幫助,如果大家有任何疑問請(qǐng)給我留言,小編會(huì)及時(shí)回復(fù)大家的。在此也非常感謝大家對(duì)腳本之家網(wǎng)站的支持!
如果你覺得本文對(duì)你有幫助,歡迎轉(zhuǎn)載,煩請(qǐng)注明出處,謝謝!

您可能感興趣的文章:
  • PHP+Redis 消息隊(duì)列 實(shí)現(xiàn)高并發(fā)下注冊(cè)人數(shù)統(tǒng)計(jì)的實(shí)例
  • 利用Redis統(tǒng)計(jì)網(wǎng)站在線活躍用戶的方法
  • PHP使用redis實(shí)現(xiàn)統(tǒng)計(jì)緩存mysql壓力的方法
  • Redis中統(tǒng)計(jì)各種數(shù)據(jù)大小的方法
  • 基于redis實(shí)現(xiàn)token驗(yàn)證用戶是否登陸
  • redis開啟和禁用登陸密碼校驗(yàn)的方法
  • 基于Redis位圖實(shí)現(xiàn)系統(tǒng)用戶登錄統(tǒng)計(jì)

標(biāo)簽:泰州 定州 畢節(jié) 南寧 甘南 拉薩 伊春 河源

巨人網(wǎng)絡(luò)通訊聲明:本文標(biāo)題《redis 實(shí)現(xiàn)登陸次數(shù)限制的思路詳解》,本文關(guān)鍵詞  redis,實(shí)現(xiàn),登陸,次數(shù),限制,;如發(fā)現(xiàn)本文內(nèi)容存在版權(quán)問題,煩請(qǐng)?zhí)峁┫嚓P(guān)信息告之我們,我們將及時(shí)溝通與處理。本站內(nèi)容系統(tǒng)采集于網(wǎng)絡(luò),涉及言論、版權(quán)與本站無關(guān)。
  • 相關(guān)文章
  • 下面列出與本文章《redis 實(shí)現(xiàn)登陸次數(shù)限制的思路詳解》相關(guān)的同類信息!
  • 本頁收集關(guān)于redis 實(shí)現(xiàn)登陸次數(shù)限制的思路詳解的相關(guān)信息資訊供網(wǎng)民參考!
  • 推薦文章