Spring Security實(shí)現(xiàn)自動(dòng)登陸功能示例
當(dāng)我們?cè)诘卿浵馫Q郵箱這種大多數(shù)的網(wǎng)站,往往在登錄按鍵上會(huì)有下次自動(dòng)登錄這個(gè)選項(xiàng),勾選后登錄成功,在一段時(shí)間內(nèi),即便退出瀏覽器或者服務(wù)器重啟,再次訪問(wèn)不需要用戶輸入賬號(hào)密碼進(jìn)行登錄,這也解決了用戶每次輸入賬號(hào)密碼的麻煩。
接下來(lái)實(shí)現(xiàn)自動(dòng)登陸。
applicatio.properties配置用戶名密碼
spring.security.user.name=java spring.security.user.password=java
controller層實(shí)現(xiàn)
@RestController public class HelloController { @GetMapping("/hello") public String hello() { return "hello"; } }
配置類實(shí)現(xiàn)
@Configuration public class SecurityConfig extends WebSecurityConfigurerAdapter { @Override protected void configure(HttpSecurity http) throws Exception { http.formLogin() .and() .authorizeRequests() .anyRequest() .authenticated() .and() .rememberMe() .and() .csrf().disable(); }
訪問(wèn)http://localhost:8080/hello,此時(shí)系統(tǒng)會(huì)重定向到登錄頁(yè)面。
二話不說(shuō),輸入賬號(hào)密碼,開(kāi)搞!
此時(shí)看到了登錄數(shù)據(jù)remember-me的值為on,當(dāng)自定義登陸框的時(shí)候應(yīng)該知道如何定義key了吧。
在hello接口,可以很清楚的看到cookie里保存了一個(gè)remember-me的令牌,這個(gè)就是自動(dòng)登錄的關(guān)鍵所在。
至于令牌是怎么生成的,先看一段源碼。核心處理類TokenBasedRememberMeServices
->onLoginSuccess
public void onLoginSuccess(HttpServletRequest request, HttpServletResponse response, Authentication successfulAuthentication) { //拿到用戶名和密碼 String username = this.retrieveUserName(successfulAuthentication); String password = this.retrievePassword(successfulAuthentication); //用戶名為空 打印日志 if (!StringUtils.hasLength(username)) { this.logger.debug("Unable to retrieve username"); } else { //密碼為空 通過(guò)用戶名再去查詢 if (!StringUtils.hasLength(password)) { UserDetails user = this.getUserDetailsService().loadUserByUsername(username); password = user.getPassword(); //查到的密碼還為空 打印日志 結(jié)束 if (!StringUtils.hasLength(password)) { this.logger.debug("Unable to obtain password for user: " + username); return; } } //令牌有效期的生成 1209600是兩周 也就是說(shuō)令牌有效期14天 int tokenLifetime = this.calculateLoginLifetime(request, successfulAuthentication); long expiryTime = System.currentTimeMillis(); expiryTime += 1000L * (long)(tokenLifetime < 0 ? 1209600 : tokenLifetime); //生成簽名 signature String signatureValue = this.makeTokenSignature(expiryTime, username, password); //設(shè)置cookie this.setCookie(new String[]{username, Long.toString(expiryTime), signatureValue}, tokenLifetime, request, response); if (this.logger.isDebugEnabled()) { this.logger.debug("Added remember-me cookie for user '" + username + "', expiry: '" + new Date(expiryTime) + "'"); } } } //使用MD5加密 通過(guò)用戶名、令牌有效期、密碼和key生成rememberMe的令牌 這里的key也就是加密的鹽值 protected String makeTokenSignature(long tokenExpiryTime, String username, String password) { String data = username + ":" + tokenExpiryTime + ":" + password + ":" + this.getKey(); try { MessageDigest digest = MessageDigest.getInstance("MD5"); return new String(Hex.encode(digest.digest(data.getBytes()))); } catch (NoSuchAlgorithmException var7) { throw new IllegalStateException("No MD5 algorithm available!"); } }
看完了核心的源碼,也就知道了令牌的生成規(guī)則:username + “:” + tokenExpiryTime + “:” + password + “:” + key(key 是一個(gè)散列鹽值,可以用來(lái)防治令牌被修改,通過(guò)MD5散列函數(shù)生成。),然后通過(guò)Base64編碼。
取出剛才的remember-me=amF2YToxNjM3MTI2MDk1OTMxOmQ5OGI3OTY5OTE4ZmQwMzE3ZWUyY2U4Y2MzMjQxZGQ0
進(jìn)行下驗(yàn)證。
解碼后是java:1637126095931:d98b7969918fd0317ee2ce8cc3241dd4
,很明顯java
是username
,1637126095931
是兩周后的tokenExpiryTime
,d98b7969918fd0317ee2ce8cc3241dd4
是password
和key
值的MD5加密生成的。
需要注意的是key值是通過(guò)UUID隨機(jī)生成的,當(dāng)重啟服務(wù)器時(shí),UUID的變化會(huì)導(dǎo)致自動(dòng)登錄失敗,所以為了避免之前生成的令牌失效,可以在配置中定義key值。
@Override protected void configure(HttpSecurity http) throws Exception { http.formLogin() .and() .authorizeRequests() .anyRequest() .authenticated() .and() .rememberMe() .key("HelloWorld") .and() .csrf().disable(); }
在Spring Security—登陸流程分析曾經(jīng)說(shuō)到 Spring Security中的認(rèn)證授權(quán)都是通過(guò)過(guò)濾器來(lái)實(shí)現(xiàn)的。RememberMeAuthenticationFilter 是自動(dòng)登錄的核心過(guò)濾器。
public class RememberMeAuthenticationFilter extends GenericFilterBean implements ApplicationEventPublisherAware { private void doFilter(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws IOException, ServletException { //獲取當(dāng)前用戶實(shí)例 繼續(xù)過(guò)濾校驗(yàn) if (SecurityContextHolder.getContext().getAuthentication() != null) { this.logger.debug(LogMessage .of(() -> "SecurityContextHolder not populated with remember-me token, as it already contained: '" + SecurityContextHolder.getContext().getAuthentication() + "'")); chain.doFilter(request, response); return; } //登錄獲取Auth Authentication rememberMeAuth = this.rememberMeServices.autoLogin(request, response); if (rememberMeAuth != null) { // Attempt authenticaton via AuthenticationManager try { //進(jìn)行remember-me校驗(yàn) rememberMeAuth = this.authenticationManager.authenticate(rememberMeAuth); // Store to SecurityContextHolder //保存用戶實(shí)例 SecurityContextHolder.getContext().setAuthentication(rememberMeAuth); //成功頁(yè)面跳轉(zhuǎn) onSuccessfulAuthentication(request, response, rememberMeAuth); this.logger.debug(LogMessage.of(() -> "SecurityContextHolder populated with remember-me token: '" + SecurityContextHolder.getContext().getAuthentication() + "'")); if (this.eventPublisher != null) { this.eventPublisher.publishEvent(new InteractiveAuthenticationSuccessEvent( SecurityContextHolder.getContext().getAuthentication(), this.getClass())); } if (this.successHandler != null) { this.successHandler.onAuthenticationSuccess(request, response, rememberMeAuth); return; } } catch (AuthenticationException ex) { this.logger.debug(LogMessage .format("SecurityContextHolder not populated with remember-me token, as AuthenticationManager " + "rejected Authentication returned by RememberMeServices: '%s'; " + "invalidating remember-me token", rememberMeAuth), ex); this.rememberMeServices.loginFail(request, response); //失敗頁(yè)面跳轉(zhuǎn) onUnsuccessfulAuthentication(request, response, ex); } } chain.doFilter(request, response); } }
@Override public final Authentication autoLogin(HttpServletRequest request, HttpServletResponse response) { //獲取cookie String rememberMeCookie = extractRememberMeCookie(request); if (rememberMeCookie == null) { return null; } this.logger.debug("Remember-me cookie detected"); if (rememberMeCookie.length() == 0) { this.logger.debug("Cookie was empty"); cancelCookie(request, response); return null; } try { //解碼cookie 拿到令牌 String[] cookieTokens = decodeCookie(rememberMeCookie); //通過(guò)令牌獲取UserdDetails UserDetails user = processAutoLoginCookie(cookieTokens, request, response); this.userDetailsChecker.check(user); this.logger.debug("Remember-me cookie accepted"); return createSuccessfulAuthentication(request, user); } catch (CookieTheftException ex) { cancelCookie(request, response); throw ex; } catch (UsernameNotFoundException ex) { this.logger.debug("Remember-me login was valid but corresponding user not found.", ex); } catch (InvalidCookieException ex) { this.logger.debug("Invalid remember-me cookie: " + ex.getMessage()); } catch (AccountStatusException ex) { this.logger.debug("Invalid UserDetails: " + ex.getMessage()); } catch (RememberMeAuthenticationException ex) { this.logger.debug(ex.getMessage()); } cancelCookie(request, response); return null; }
大致整體流程就是如果拿不到實(shí)例,則進(jìn)行remember-me驗(yàn)證,通過(guò)autoLogin方法里獲取cookie,解析令牌,拿到Auth,最后進(jìn)行校驗(yàn)。之后剩下的和登陸流程分析的差不多。
到此這篇關(guān)于Spring Security實(shí)現(xiàn)自動(dòng)登陸功能示例的文章就介紹到這了,更多相關(guān)Spring Security 自動(dòng)登陸內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
Java實(shí)現(xiàn)線程按序交替執(zhí)行的方法詳解
這篇文章主要為大家詳細(xì)介紹了Java如何實(shí)現(xiàn)線程按序交替執(zhí)行,文中的示例代碼講解詳細(xì),對(duì)我們了解線程有一定幫助,需要的可以參考一下2022-10-10一篇文章帶你了解spring事務(wù)失效的多種場(chǎng)景
在日常編碼過(guò)程中常常涉及到事務(wù),在前兩天看到一篇文章提到了Spring事務(wù),那么在此總結(jié)下在Spring環(huán)境下事務(wù)失效的幾種原因.2021-09-09Java并發(fā)編程之volatile與JMM多線程內(nèi)存模型
這篇文章主要介紹了Java并發(fā)volatile與JMM多線程內(nèi)存模型,本文通過(guò)實(shí)例代碼給大家介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或工作具有一定的參考借鑒價(jià)值,需要的朋友可以參考下2022-05-05