[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"\u002Fresource\u002Fdocument\u002Flist?undefined":3,"\u002Fresource\u002Fdocument\u002Fquery\u002Fu8ekxxucowr2b1tm?undefined":462,"\u002Fresource\u002Fadvertise\u002Flist?type=all?undefined":465},{"data":4,"status":460,"success":461},[5,148,202,291,332,370,420],{"books":6,"desc":145,"id":8,"image":146,"title":147},[7,40,63,78,93,105,117],{"cateId":8,"chapters":9,"desc":36,"id":11,"time":37,"title":38,"video":39},1,[10,15,18,21,24,27,30,33],{"bookId":11,"id":12,"indexOrder":13,"name":14},24,"8egfulw98v3h680j",0,"JavaSE 笔记（一）走进Java语言",{"bookId":11,"id":16,"indexOrder":13,"name":17},"pew6po6wrou23pk3","JavaSE 笔记（二）面向过程编程",{"bookId":11,"id":19,"indexOrder":13,"name":20},"eldst1fgrbdkmfs7","JavaSE 笔记（三）面向对象基础",{"bookId":11,"id":22,"indexOrder":13,"name":23},"48zphgkpjto8cath","JavaSE 笔记（四）面向对象高级篇",{"bookId":11,"id":25,"indexOrder":13,"name":26},"6r4llai92yc15j98","JavaSE 笔记（五）泛型程序设计",{"bookId":11,"id":28,"indexOrder":13,"name":29},"k6fmxd6qabgkwm9i","JavaSE 笔记（六）集合类与IO",{"bookId":11,"id":31,"indexOrder":13,"name":32},"qrd0xfttsz32gpqg","JavaSE 笔记（七）多线程与反射",{"bookId":11,"id":34,"indexOrder":13,"name":35},"td5tgn04nqmkrryt","JavaSE 笔记（八）GUI程序开发","基于Java25全新录制的SE课程",2025,"JavaSE 核心内容","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV163GGz2E8c",{"cateId":8,"chapters":41,"desc":59,"id":8,"time":60,"title":61,"video":62},[42,44,46,49,51,53,55,57],{"bookId":8,"id":43,"indexOrder":13,"name":14},"ibeeuwsbbi00undq",{"bookId":8,"id":45,"indexOrder":13,"name":17},"dncxjecdv4wciqcp",{"bookId":8,"id":47,"indexOrder":13,"name":48},"jviyz2hsht9ete5k","JavaSE 笔记（三）面向对象基础篇",{"bookId":8,"id":50,"indexOrder":13,"name":23},"qb9i6q9fap7bg1cc",{"bookId":8,"id":52,"indexOrder":13,"name":26},"hnkrjrkm3hjzeq6s",{"bookId":8,"id":54,"indexOrder":13,"name":29},"erpm32wduoaaqmrx",{"bookId":8,"id":56,"indexOrder":13,"name":32},"lfqtvxr7azumcwja",{"bookId":8,"id":58,"indexOrder":13,"name":35},"qs7gqok56gzc6idr","2022年制作的JavaSE版本",2022,"JavaSE 22年旧版","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1YP4y1o75f\u002F",{"cateId":8,"chapters":64,"desc":75,"id":66,"time":60,"title":76,"video":77},[65,69,72],{"bookId":66,"id":67,"indexOrder":13,"name":68},2,"g96k66kczovvbm1i","JVM 笔记（一）走进JVM",{"bookId":66,"id":70,"indexOrder":13,"name":71},"ydd7n3jg8unc3clg","JVM 笔记（二）内存管理",{"bookId":66,"id":73,"indexOrder":13,"name":74},"r9dq37de0kaeauoi","JVM 笔记（三）类与类加载","了解Java的底层运作机制","Java JVM 虚拟机","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Er4y1r7as\u002F",{"cateId":8,"chapters":79,"desc":90,"id":81,"time":60,"title":91,"video":92},[80,84,87],{"bookId":81,"id":82,"indexOrder":13,"name":83},3,"asncyye9ya18gfar","JUC 笔记（一）再谈多线程",{"bookId":81,"id":85,"indexOrder":13,"name":86},"5tr1sm4ho6ygpt9q","JUC 笔记（二）并发编程核心",{"bookId":81,"id":88,"indexOrder":13,"name":89},"1scf51z5300mzxkh","JUC 笔记（三）并发编程进阶","你也可以成为多线程的主宰者","Java JUC 并发编程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1JT4y1S7K8\u002F",{"cateId":8,"chapters":94,"desc":102,"id":96,"time":60,"title":103,"video":104},[95,99],{"bookId":96,"id":97,"indexOrder":13,"name":98},4,"eedesc445ygiqhil","NIO 笔记（一）基础内容",{"bookId":96,"id":100,"indexOrder":13,"name":101},"ndz9t0uunrmfmv4n","NIO 笔记（二）Netty框架专题","编写畅快的高性能网络服务器","Java NIO 网络编程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1ar4y1J7mC\u002F",{"cateId":8,"chapters":106,"desc":114,"id":108,"time":60,"title":115,"video":116},[107,111],{"bookId":108,"id":109,"indexOrder":13,"name":110},5,"9890i8ofuadpwy2b","[扩展篇] Java 9-17新特性介绍",{"bookId":108,"id":112,"indexOrder":13,"name":113},"tsrkqvb6zpmtwh0n","[扩展篇] JavaSE关键字总结 笔记","精彩仍在继续，不要停止脚步","其他内容","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1tU4y1y7Fg\u002F",{"cateId":8,"chapters":118,"desc":141,"id":120,"time":142,"title":143,"video":144},[119,123,126,129,132,135,138],{"bookId":120,"id":121,"indexOrder":13,"name":122},6,"4db9h32opv7imszh","JavaSE 笔记（一）面向过程编程",{"bookId":120,"id":124,"indexOrder":13,"name":125},"c93u3v37br7hgn1q","JavaSE 笔记（二）面向对象基础篇",{"bookId":120,"id":127,"indexOrder":13,"name":128},"yglsjde9gi1jxkcb","JavaSE 笔记（三）泛型与集合类",{"bookId":120,"id":130,"indexOrder":13,"name":131},"ilhi987n986rmvo3","JavaSE 笔记（四）异常机制",{"bookId":120,"id":133,"indexOrder":13,"name":134},"pqv38vexmenglk4k","JavaSE 笔记（五）IO",{"bookId":120,"id":136,"indexOrder":13,"name":137},"jiq41n87i9ia7ilw","JavaSE 笔记（六）多线程",{"bookId":120,"id":139,"indexOrder":13,"name":140},"wn7x2mge9ws79zps","JavaSE 笔记（七）反射","此版本为早期录制的旧版本",2021,"JavaSE 21年旧版","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Gv411T7pi\u002F","包含JavaSE基础路线全部教程笔记，打下坚实的基础","https:\u002F\u002Fpic2.zhimg.com\u002F80\u002Fv2-bf1a927f037a79f4d57d9ae543430a0d_1440w.webp","JavaSE 系列笔记 ☕️",{"books":149,"desc":199,"id":66,"image":200,"title":201},[150,166,178],{"cateId":66,"chapters":151,"desc":162,"id":153,"time":163,"title":164,"video":165},[152,156,159],{"bookId":153,"id":154,"indexOrder":13,"name":155},21,"iqbc2haub31bwqtz","Lombok 极速上手",{"bookId":153,"id":157,"indexOrder":13,"name":158},"ijay2hay19kn1k031","Mybatis 快速上手",{"bookId":153,"id":160,"indexOrder":13,"name":161},"ru4ogh2waocpn4jo","Maven 快速上手","JavaWeb阶段必须扩展知识点",2024,"常用知识讲解","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1gb421J7ok\u002F",{"cateId":66,"chapters":167,"desc":175,"id":169,"time":163,"title":176,"video":177},[168,172],{"bookId":169,"id":170,"indexOrder":13,"name":171},22,"ek20yvb6huhxizx7","JavaWeb 笔记（一）计算机网络基础",{"bookId":169,"id":173,"indexOrder":13,"name":174},"pgevws6w2krkffa4","JavaWeb笔记（二）Java与数据库","全面升级的JavaWeb课程","JavaWeb 网站开发","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1kS421X7rq\u002F",{"cateId":66,"chapters":179,"desc":196,"id":181,"time":142,"title":197,"video":198},[180,184,187,190,193],{"bookId":181,"id":182,"indexOrder":13,"name":183},7,"ggwwj09j2vkfftvd","JavaWeb 笔记（一）Java网络编程",{"bookId":181,"id":185,"indexOrder":13,"name":186},"sauvq105istskjaz","JavaWeb 笔记（二）数据库基础",{"bookId":181,"id":188,"indexOrder":13,"name":189},"xgbeasmvrhxx9tn4","JavaWeb 笔记（三）Java与数据库",{"bookId":181,"id":191,"indexOrder":13,"name":192},"k7dfwua3bsezvw9q","JavaWeb 笔记（四）前端基础",{"bookId":181,"id":194,"indexOrder":13,"name":195},"ycpagby2v7j4p728","JavaWeb 笔记（五）后端开发","搭建属于自己的Web网站","JavaWeb 旧版","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1CL4y1i7qR\u002F","包含JavaWeb路线全套笔记，从零开始搭建自己的网站！","https:\u002F\u002Fpic3.zhimg.com\u002F80\u002Fv2-df3b38e3012258ed70c23b586309e3f6_1440w.webp","JavaWeb 系列笔记 🚛",{"books":203,"desc":288,"id":81,"image":289,"title":290},[204,220,235,255,273],{"cateId":81,"chapters":205,"desc":216,"id":207,"time":217,"title":218,"video":219},[206,210,213],{"bookId":207,"id":208,"indexOrder":13,"name":209},8,"h7sjo5oy0l03607e","SSM笔记（一）Spring基础",{"bookId":207,"id":211,"indexOrder":13,"name":212},"eve8gq72qmdb46sg","SSM笔记（二）SpringMvc基础",{"bookId":207,"id":214,"indexOrder":13,"name":215},"63v73g0zh1qlr6fk","SSM笔记（三）SpringSecurity基础","Spring的探索之路从这里开始",2023,"JavaSSM 基础部分","[\"https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Kv4y1x7is\u002F\", \"https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Lh4y1M7kx\u002F\", \"https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1fV411M7aS\u002F\"]",{"cateId":81,"chapters":221,"desc":232,"id":223,"time":217,"title":233,"video":234},[222,226,229],{"bookId":223,"id":224,"indexOrder":13,"name":225},16,"0k66v5r6slsfuog4","SpringBoot笔记（一）核心内容",{"bookId":223,"id":227,"indexOrder":13,"name":228},"bqlrnc2yvkaxo8s1","SpringBoot笔记（二）数据交互",{"bookId":223,"id":230,"indexOrder":13,"name":231},"wci9lb9tgea866jt","SpringBoot笔记（三）前后端分离","SpringBoot全新重制版","SpringBoot 新版","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1xu4y1m7UP\u002F",{"cateId":81,"chapters":236,"desc":252,"id":238,"time":60,"title":253,"video":254},[237,240,243,246,249],{"bookId":238,"id":239,"indexOrder":13,"name":225},9,"e43gl1ilygps032v",{"bookId":238,"id":241,"indexOrder":13,"name":242},"emnmd8nzfdb3hr50","SpringBoot笔记（二）Git版本控制",{"bookId":238,"id":244,"indexOrder":13,"name":245},"jjlolj5igvttvyhv","SpringBoot笔记（三）Redis数据库",{"bookId":238,"id":247,"indexOrder":13,"name":248},"skgr4ivb5curdoux","SpringBoot笔记（四）其他框架介绍",{"bookId":238,"id":250,"indexOrder":13,"name":251},"le91fqhu4dqui1k4","SpringBoot笔记（五）Linux系统","逐步走向企业级开发","SpringBoot 旧版","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1UL411V7f3\u002F",{"cateId":81,"chapters":256,"desc":270,"id":258,"time":60,"title":271,"video":272},[257,261,264,267],{"bookId":258,"id":259,"indexOrder":13,"name":260},10,"oejzo0l77zeb6a7e","SpringCloud笔记（一）微服务基础",{"bookId":258,"id":262,"indexOrder":13,"name":263},"f6eya9taaelsl35p","SpringCloud笔记（二）微服务进阶",{"bookId":258,"id":265,"indexOrder":13,"name":266},"35v1hbsfcdgagdnw","SpringCloud笔记（三）微服务应用",{"bookId":258,"id":268,"indexOrder":13,"name":269},"a782u84512tyuo1m","SpringCloud笔记（四）消息队列","体验微服务架构带来的魅力","SpringCloud 进阶","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1AL4y1j7RY\u002F",{"cateId":81,"chapters":274,"desc":285,"id":276,"time":142,"title":286,"video":287},[275,278,280,282],{"bookId":276,"id":277,"indexOrder":13,"name":209},11,"efjw75u8a251qxk5",{"bookId":276,"id":279,"indexOrder":13,"name":212},"guc134xb7sl78vju",{"bookId":276,"id":281,"indexOrder":13,"name":215},"u8ekxxucowr2b1tm",{"bookId":276,"id":283,"indexOrder":13,"name":284},"vkpmw9wbej21nei6","SSM笔记（四）MySQL进阶","此教程为2021年旧版教程","JavaSSM 旧版","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1xL4y1H7Tq\u002F","包含Spring全套框架笔记，从开始到Spring Boot，以及众多运维小知识。","https:\u002F\u002Fpic4.zhimg.com\u002F80\u002Fv2-28c3144421220d7c048703281bc34f63_1440w.webp","Spring 系列笔记 🍏",{"books":292,"desc":329,"id":96,"image":330,"title":331},[293,308],{"cateId":96,"chapters":294,"desc":305,"id":296,"time":60,"title":306,"video":307},[295,299,302],{"bookId":296,"id":297,"indexOrder":13,"name":298},12,"jd3e8u5cmvx5gco6","C语言（一）计算机思维导论",{"bookId":296,"id":300,"indexOrder":13,"name":301},"lqv77apvx82nkkio","C语言（二）基础语法",{"bookId":296,"id":303,"indexOrder":13,"name":304},"xb0b9t37gyv96xns","C语言（三）高级特性","包含高等院校需要教授的全部内容","C语言程序设计","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Cr4y137os\u002F",{"cateId":96,"chapters":309,"desc":326,"id":311,"time":60,"title":327,"video":328},[310,314,317,320,323],{"bookId":311,"id":312,"indexOrder":13,"name":313},13,"8a046ps2e4w6k4py","数据结构与算法（一）线性结构篇",{"bookId":311,"id":315,"indexOrder":13,"name":316},"3ma8db91f9zrnkja","数据结构与算法（二）树形结构篇",{"bookId":311,"id":318,"indexOrder":13,"name":319},"0lsjm59k7cgu4tpr","数据结构与算法（三）散列表篇",{"bookId":311,"id":321,"indexOrder":13,"name":322},"0qzy7bogo0g2pusa","数据结构与算法（四）图结构篇",{"bookId":311,"id":324,"indexOrder":13,"name":325},"6gmcxcikcilyxblj","数据结构与算法（五）排序算法篇","虽然很难，但是它是考研必学科目","数据结构与算法","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV13W4y127Ey\u002F","你的内心一直有一个坚定的声音在告诉你，一定要考上一名研究生，向着未来前进吧！","https:\u002F\u002Fpic2.zhimg.com\u002F80\u002Fv2-ac128404efb29ce1c9d1ccc61024f1d1_1440w.webp","C语言 系列笔记 🥬",{"books":333,"desc":367,"id":108,"image":368,"title":369},[334,349,358],{"cateId":108,"chapters":335,"desc":346,"id":337,"time":163,"title":347,"video":348},[336,340,343],{"bookId":337,"id":338,"indexOrder":13,"name":339},17,"urw2e6gg1lprv65w","Kotlin（一）基础语法",{"bookId":337,"id":341,"indexOrder":13,"name":342},"t7lnl87f74f3v1ju","Kotlin（二）类与对象",{"bookId":337,"id":344,"indexOrder":13,"name":345},"v1zzvki0knb1xvml","Kotlin（三）高级特性","包含Kotlin语言完整基础部分","Kotlin程序设计基础","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1P94y1c7tV\u002F",{"cateId":108,"chapters":350,"desc":355,"id":352,"time":163,"title":356,"video":357},[351],{"bookId":352,"id":353,"indexOrder":13,"name":354},18,"ovbzpe7065bye1st","Kotlin扩展（一）","包含Kotlin额外扩展知识","Kotlin扩展篇","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Hg4y1m7Ca\u002F",{"cateId":108,"chapters":359,"desc":364,"id":361,"time":163,"title":365,"video":366},[360],{"bookId":361,"id":362,"indexOrder":13,"name":363},19,"3at7ybv04dmjc0wp","Gradle基础教程","Gradle配置教程（Kotlin）","Gradle教程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1Fc411x7xF\u002F","Kotlin让JVM平台焕发新的生机，让语言的表达更加优美","https:\u002F\u002Fpic2.zhimg.com\u002F80\u002Fv2-be815568f7c79c64cdaa171b0409786d_1440w.webp","Kotlin 系列笔记 ☘️",{"books":371,"desc":418,"id":120,"title":419},[372,391,403],{"cateId":120,"chapters":373,"desc":387,"id":375,"time":388,"title":389,"video":390},[374,378,381,384],{"bookId":375,"id":376,"indexOrder":13,"name":377},26,"zjf5qapwqtqiohcn","JavaScript笔记（一）基础语法",{"bookId":375,"id":379,"indexOrder":13,"name":380},"95jc6sjyjwcp9pvp","JavaScript笔记（二）核心知识",{"bookId":375,"id":382,"indexOrder":13,"name":383},"j35cdc1qz8dzq7pn","JavaScript笔记（三）进阶知识",{"bookId":375,"id":385,"indexOrder":13,"name":386},"sdhodlihphnpcg37","JavaScript笔记（四）前端基础","包含JavaScript最新语法规范讲解",2026,"JavaScript教程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1xq6gBgESU",{"cateId":120,"chapters":392,"desc":400,"id":394,"time":37,"title":401,"video":402},[393,397],{"bookId":394,"id":395,"indexOrder":13,"name":396},23,"bsisgazdftiz3o9c","HTML5笔记（一）基础内容",{"bookId":394,"id":398,"indexOrder":13,"name":399},"njol93fs34gfwuzf","HTML5笔记（二）高级内容","包含HTML基础内容和相关知识点","HTML5核心教程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1BrBiYNEWg",{"cateId":120,"chapters":404,"desc":415,"id":406,"time":37,"title":416,"video":417},[405,409,412],{"bookId":406,"id":407,"indexOrder":13,"name":408},25,"jo74ciirtg8wh90y","CSS笔记（一）基础入门",{"bookId":406,"id":410,"indexOrder":13,"name":411},"ap5ixyomoejuw4ue","CSS笔记（二）盒模型和布局",{"bookId":406,"id":413,"indexOrder":13,"name":414},"4djgk5xy1lzpiuf2","CSS笔记（三）变换和过渡","包含CSS3基础内容和相关知识点","CSS3核心教程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1sQeEzFEKi","包含Web前端学习路径全部教程笔记，打下坚实的基础","Web前端 系列笔记",{"books":421,"desc":458,"id":423,"image":368,"title":459},[422,432,450],{"cateId":423,"chapters":424,"desc":429,"id":426,"time":163,"title":430,"video":431},100,[425],{"bookId":426,"id":427,"indexOrder":13,"name":428},20,"o0ab271mkdsas87","Markdown基础语法","编写简洁而又优美的文档","Markdown教程","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1eJ4m157kC",{"cateId":423,"chapters":433,"desc":447,"id":435,"time":60,"title":448,"video":449},[434,438,441,444],{"bookId":435,"id":436,"indexOrder":13,"name":437},14,"6386mh7anqt4tzyv","设计模式（一）面向对象设计原则",{"bookId":435,"id":439,"indexOrder":13,"name":440},"8ftkb38wfn6ox0ug","设计模式（二）创建型",{"bookId":435,"id":442,"indexOrder":13,"name":443},"i1msql1k8y70etey","设计模式（三）结构型",{"bookId":435,"id":445,"indexOrder":13,"name":446},"5434a3cyyjvwhs8s","设计模式（四）行为型","使你的编码水平得到质的飞跃","设计模式系列","https:\u002F\u002Fwww.bilibili.com\u002Fvideo\u002FBV1u3411P7Na\u002F",{"cateId":423,"chapters":451,"desc":456,"id":453,"time":60,"title":457},[452],{"bookId":453,"id":454,"indexOrder":13,"name":455},15,"zj9uvg0sp3b0sok8","Docker 容器技术 笔记","这里包含其他中间件课程笔记","其他中间件笔记","我们对知识的探索从未停止，只有不断地学习，才能走向美好的未来！","其他笔记分类 🌽",200,true,{"data":463,"status":460,"success":461},{"bookId":276,"content":464,"id":281,"indexOrder":81,"name":215},"![img](https:\u002F\u002Fs2.loli.net\u002F2023\u002F08\u002F14\u002FRdwC9Nn6cfUZPjm.jpg)\n\n# SpringSecurity\n\n本章我们会一边讲解SpringSecurity框架，一边从头开始编写图书管理系统。\n\n  SpringSecurity是一个基于Spring开发的非常强大的权限验证框架，其核心功能包括：\n\n- 认证 （用户登录）\n- 授权 （此用户能够做哪些事情）\n- 攻击防护 （防止伪造身份攻击）\n\n我们为什么需要使用更加专业的全新验证框架，还要从CSRF说起。\n\n## CSRF跨站请求伪造攻击\n\n我们时常会在QQ上收到别人发送的钓鱼网站链接，只要你在上面登陆了你的QQ账号，那么不出意外，你的号已经在别人手中了。实际上这一类网站都属于恶意网站，专门用于盗取他人信息，执行非法操作，甚至获取他人账户中的财产，非法转账等。而这里，我们需要了解一种比较容易发生的恶意操作，从不法分子的角度去了解整个流程。\n\n我们在JavaWeb阶段已经了解了Session和Cookie的机制，在一开始的时候，服务端会给浏览器一个名为JSESSION的Cookie信息作为会话的唯一凭据，只要用户携带此Cookie访问我们的网站，那么我们就可以认定此会话属于哪个浏览器。因此，只要此会话的用户执行了登录操作，那么就可以随意访问个人信息等内容。\n\n比如现在，我们的服务器新增了一个转账的接口，用户登录之后，只需要使用POST请求携带需要转账的金额和转账人访问此接口就可以进行转账操作：\n\n```java\n@RequestMapping(\"\u002Findex\")\npublic String index(HttpSession session){\n    session.setAttribute(\"login\", true);   \u002F\u002F这里就正常访问一下index表示登陆\n    return \"index\";\n}\n```\n\n```java\n@RequestMapping(value = \"\u002Fpay\", method = RequestMethod.POST, produces = \"text\u002Fhtml;charset=utf-8\") \u002F\u002F这里要设置一下produces不然会乱码\n@ResponseBody\npublic String pay(String account,\n                  int amount,\n                  @SessionAttribute(\"login\") Boolean isLogin){\n    if (isLogin) return \"成功转账 ￥\"+amount+\" 给：\"+account;\n    else return \"转账失败，您没有登陆！\";\n}\n```\n\n那么，大家有没有想过这样一个问题，我们为了搜索学习资料时可能一不小心访问了一个恶意网站，而此网站携带了这样一段内容：\n\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n    \u003Cmeta charset=\"UTF-8\">\n    \u003Ctitle>我是(恶)学(意)习网站\u003C\u002Ftitle>\n\u003C\u002Fhead>\n\u003Cbody>\n    \u003Cdiv>\n        \u003Cdiv>对不起，您还没有充值本站的学习会员，请先充值后再观看学习视频\u003C\u002Fdiv>\n        \u003Cform action=\"http:\u002F\u002Flocalhost:8080\u002Fmvc\u002Fpay\" method=\"post\">\n            \u003Cinput type=\"text\" name=\"account\" value=\"hacker\" hidden>\n            \u003Cinput type=\"number\" name=\"amount\" value=\"666666\" hidden>\n            \u003Cinput type=\"submit\" value=\"点我充值会员，观看完整视频\">\n        \u003C\u002Fform>\n    \u003C\u002Fdiv>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n注意这个页面并不是我们官方提供的页面，而是不法分子搭建的恶意网站。我们发现此页面中有一个表单，但是表单中的两个输入框被隐藏了，而我们看到的只有一个按钮，我们不知道这是一个表单，也不知道表单会提交给那个地址，这时整个页面就非常有迷惑性了。如果我们点击此按钮，那么整个表单的数据会以POST的形式发送给我们的服务端（会携带之前登陆我们网站的Cookie信息），但是这里很明显是另一个网站跳转，通过这样的方式，恶意网站就成功地在我们毫不知情的情况下引导我们执行了转账操作，当你发现上当受骗时，钱已经被转走了。\n\n而这种构建恶意页面，引导用户访问对应网站执行操作的方式称为：**跨站请求伪造**（CSRF，Cross Site Request Forgery）\n\n显然，我们之前编写的图书管理系统就存在这样的安全漏洞，而SpringSecurity就很好地解决了这样的问题。\n\n***\n\n## 开发环境搭建\n\n我们依然使用之前的模板来搭建图书管理系统项目。\n\n导入以下依赖：\n\n```xml\n\u003C!-- 建议为各个依赖进行分类，到后期我们的项目可能会导入很多依赖，添加注释会大幅度提高阅读效率 -->\n\u003Cdependencies>\n    \u003C!--  Spring框架依赖  -->\n    \u003Cdependency>\n        \u003CgroupId>org.springframework.security\u003C\u002FgroupId>\n        \u003CartifactId>spring-security-web\u003C\u002FartifactId>\n        \u003Cversion>5.5.3\u003C\u002Fversion>\n    \u003C\u002Fdependency>\n  \t\u003Cdependency>\n        \u003CgroupId>org.springframework.security\u003C\u002FgroupId>\n        \u003CartifactId>spring-security-config\u003C\u002FartifactId>\n        \u003Cversion>5.5.3\u003C\u002Fversion>\n    \u003C\u002Fdependency>\n    \u003Cdependency>\n        \u003CgroupId>org.springframework\u003C\u002FgroupId>\n        \u003CartifactId>spring-webmvc\u003C\u002FartifactId>\n        \u003Cversion>5.3.14\u003C\u002Fversion>\n    \u003C\u002Fdependency>\n\n    \u003C!--  持久层框架依赖  -->\n\t\t\u003Cdependency>\n            \u003CgroupId>mysql\u003C\u002FgroupId>\n            \u003CartifactId>mysql-connector-java\u003C\u002FartifactId>\n            \u003Cversion>8.0.27\u003C\u002Fversion>\n        \u003C\u002Fdependency>\n        \u003Cdependency>\n            \u003CgroupId>org.mybatis\u003C\u002FgroupId>\n            \u003CartifactId>mybatis-spring\u003C\u002FartifactId>\n            \u003Cversion>2.0.6\u003C\u002Fversion>\n        \u003C\u002Fdependency>\n        \u003Cdependency>\n            \u003CgroupId>org.mybatis\u003C\u002FgroupId>\n            \u003CartifactId>mybatis\u003C\u002FartifactId>\n            \u003Cversion>3.5.7\u003C\u002Fversion>\n        \u003C\u002Fdependency>\n        \u003Cdependency>\n            \u003CgroupId>org.springframework\u003C\u002FgroupId>\n            \u003CartifactId>spring-jdbc\u003C\u002FartifactId>\n            \u003Cversion>5.3.14\u003C\u002Fversion>\n        \u003C\u002Fdependency>\n        \u003Cdependency>\n            \u003CgroupId>com.zaxxer\u003C\u002FgroupId>\n            \u003CartifactId>HikariCP\u003C\u002FartifactId>\n            \u003Cversion>3.4.5\u003C\u002Fversion>\n        \u003C\u002Fdependency>\n\n    \u003C!--  其他工具框架依赖：Lombok、Slf4j  -->\n    \u003Cdependency>\n        \u003CgroupId>org.projectlombok\u003C\u002FgroupId>\n        \u003CartifactId>lombok\u003C\u002FartifactId>\n        \u003Cversion>1.18.22\u003C\u002Fversion>\n    \u003C\u002Fdependency>\n    \u003Cdependency>\n        \u003CgroupId>org.slf4j\u003C\u002FgroupId>\n        \u003CartifactId>slf4j-jdk14\u003C\u002FartifactId>\n        \u003Cversion>1.7.32\u003C\u002Fversion>\n    \u003C\u002Fdependency>\n\n    \u003C!--  ServletAPI  -->\n    \u003Cdependency>\n        \u003CgroupId>javax.servlet\u003C\u002FgroupId>\n        \u003CartifactId>javax.servlet-api\u003C\u002FartifactId>\n        \u003Cversion>4.0.1\u003C\u002Fversion>\n        \u003Cscope>provided\u003C\u002Fscope>\n    \u003C\u002Fdependency>\n\n    \u003C!--  JUnit依赖  -->\n    \u003Cdependency>\n        \u003CgroupId>org.junit.jupiter\u003C\u002FgroupId>\n        \u003CartifactId>junit-jupiter-api\u003C\u002FartifactId>\n        \u003Cversion>${junit.version}\u003C\u002Fversion>\n        \u003Cscope>test\u003C\u002Fscope>\n    \u003C\u002Fdependency>\n    \u003Cdependency>\n        \u003CgroupId>org.junit.jupiter\u003C\u002FgroupId>\n        \u003CartifactId>junit-jupiter-engine\u003C\u002FartifactId>\n        \u003Cversion>${junit.version}\u003C\u002Fversion>\n        \u003Cscope>test\u003C\u002Fscope>\n    \u003C\u002Fdependency>\n\u003C\u002Fdependencies>\n```\n\n接着创建Initializer来配置Web应用程序：\n\n```java\npublic class MvcInitializer extends AbstractAnnotationConfigDispatcherServletInitializer {\n\n    @Override\n    protected Class\u003C?>[] getRootConfigClasses() {\n        return new Class[]{RootConfiguration.class};\n    }\n\n    @Override\n    protected Class\u003C?>[] getServletConfigClasses() {\n        return new Class[]{MvcConfiguration.class};\n    }\n\n    @Override\n    protected String[] getServletMappings() {\n        return new String[]{\"\u002F\"};\n    }\n}\n```\n\n创建Mvc配置类：\n\n```java\n@ComponentScan(\"book.manager.controller\")\n@Configuration\n@EnableWebMvc\npublic class MvcConfiguration implements WebMvcConfigurer {\n\n    \u002F\u002F我们需要使用ThymeleafViewResolver作为视图解析器，并解析我们的HTML页面\n    @Bean\n    public ThymeleafViewResolver thymeleafViewResolver(@Autowired SpringTemplateEngine springTemplateEngine){\n        ThymeleafViewResolver resolver = new ThymeleafViewResolver();\n        resolver.setOrder(1);\n        resolver.setCharacterEncoding(\"UTF-8\");\n        resolver.setTemplateEngine(springTemplateEngine);\n        return resolver;\n    }\n\n    \u002F\u002F配置模板解析器\n    @Bean\n    public SpringResourceTemplateResolver templateResolver(){\n        SpringResourceTemplateResolver resolver = new SpringResourceTemplateResolver();\n        resolver.setSuffix(\".html\");\n        resolver.setPrefix(\"\u002FWEB-INF\u002Ftemplate\u002F\");\n        return resolver;\n    }\n\n    \u002F\u002F配置模板引擎Bean\n    @Bean\n    public SpringTemplateEngine springTemplateEngine(@Autowired ITemplateResolver resolver){\n        SpringTemplateEngine engine = new SpringTemplateEngine();\n        engine.setTemplateResolver(resolver);\n        return engine;\n    }\n\n    \u002F\u002F开启静态资源处理\n    @Override\n    public void configureDefaultServletHandling(DefaultServletHandlerConfigurer configurer) {\n        configurer.enable();\n    }\n\n    \u002F\u002F静态资源路径配置\n    @Override\n    public void addResourceHandlers(ResourceHandlerRegistry registry) {\n        registry.addResourceHandler(\"\u002Fstatic\u002F**\").addResourceLocations(\"\u002FWEB-INF\u002Fstatic\u002F\");\n    }\n}\n```\n\n创建Root配置类：\n\n```java\n@Configuration\npublic class RootConfiguration {\n\n}\n```\n\n最后创建一个专用于响应页面的Controller即可：\n\n```java\n\u002F**\n * 专用于处理页面响应的控制器\n *\u002F\n@Controller\npublic class PageController {\n\n    @RequestMapping(\"\u002Findex\")\n    public String login(){\n        return \"index\";\n    }\n}\n```\n\n接着我们需要将前端页面放到对应的文件夹中，然后开启服务器并通过浏览器，成功访问。\n\n接着我们需要配置SpringSecurity，与Mvc一样，需要一个初始化器：\n\n```java\npublic class SecurityInitializer extends AbstractSecurityWebApplicationInitializer {\n    \u002F\u002F不用重写任何内容\n  \t\u002F\u002F这里实际上会自动注册一个Filter，SpringSecurity底层就是依靠N个过滤器实现的，我们之后再探讨\n}\n```\n\n接着我们需要再创建一个配置类用于配置SpringSecurity：\n\n```java\n@Configuration\n@EnableWebSecurity\npublic class SecurityConfiguration extends WebSecurityConfigurerAdapter {\n\t\t\u002F\u002F继承WebSecurityConfigurerAdapter，之后会进行配置\n}\n```\n\n接着在根容器中添加此配置文件即可：\n\n```java\n@Override\nprotected Class\u003C?>[] getRootConfigClasses() {\n    return new Class[]{RootConfiguration.class, SecurityConfiguration.class};\n}\n```\n\n这样，SpringSecurity的配置就完成了，我们再次运行项目，会发现无法进入的我们的页面中，无论我们访问哪个页面，都会进入到SpringSecurity为我们提供的一个默认登录页面，之后我们会讲解如何进行配置。\n\n至此，项目环境搭建完成。\n\n***\n\n## 认证\n\n### 直接认证\n\n既然我们的图书管理系统要求用户登录之后才能使用，所以我们首先要做的就是实现用户验证，要实现用户验证，我们需要进行一些配置：\n\n```java\n@Override\nprotected void configure(AuthenticationManagerBuilder auth) throws Exception {\n    BCryptPasswordEncoder encoder = new BCryptPasswordEncoder();  \u002F\u002F这里使用SpringSecurity提供的BCryptPasswordEncoder\n    auth\n            .inMemoryAuthentication() \u002F\u002F直接验证方式，之后会讲解使用数据库验证\n            .passwordEncoder(encoder) \u002F\u002F密码加密器\n            .withUser(\"test\")   \u002F\u002F用户名\n            .password(encoder.encode(\"123456\"))   \u002F\u002F这里需要填写加密后的密码\n            .roles(\"user\");   \u002F\u002F用户的角色（之后讲解）\n}\n```\n\nSpringSecurity的密码校验并不是直接使用原文进行比较，而是使用加密算法将密码进行加密（更准确地说应该进行Hash处理，此过程是不可逆的，无法解密），最后将用户提供的密码以同样的方式加密后与密文进行比较。对于我们来说，用户提供的密码属于隐私信息，直接明文存储并不好，而且如果数据库内容被窃取，那么所有用户的密码将全部泄露，这是我们不希望看到的结果，我们需要一种既能隐藏用户密码也能完成认证的机制，而Hash处理就是一种很好的解决方案，通过将用户的密码进行Hash值计算，计算出来的结果无法还原为原文，如果需要验证是否与此密码一致，那么需要以同样的方式加密再比较两个Hash值是否一致，这样就很好的保证了用户密码的安全性。\n\n![image-20230814162400333](https:\u002F\u002Fs2.loli.net\u002F2023\u002F08\u002F14\u002FRfEQFX2dk4xUu6e.png)\n\n我们这里使用的是SpringSecurity提供的BCryptPasswordEncoder，至于加密过程，这里不做深入讲解。\n\n现在，我们可以尝试使用此账号登录，在登录后，就可以随意访问我们的网站内容了。\n\n### 使用数据库认证\n\n前面我们已经实现了直接认证的方式，那么如何将其连接到数据库，通过查询数据库中的内容来进行用户登录呢？\n\n首先我们需要将加密后的密码添加到数据库中作为用户密码：\n\n```java\npublic class MainTest {\n\n    @Test\n    public void test(){\n        BCryptPasswordEncoder encoder = new BCryptPasswordEncoder();\n        System.out.println(encoder.encode(\"123456\"));\n    }\n}\n```\n\n这里编写一个测试来完成。\n\n然后我们需要创建一个Service实现，实现的是UserDetailsService，它支持我们自己返回一个UserDetails对象，我们只需直接返回一个包含数据库中的用户名、密码等信息的UserDetails即可，SpringSecurity会自动进行比对。\n\n```java\n@Service\npublic class UserAuthService implements UserDetailsService {\n\n    @Resource\n    UserMapper mapper;\n\n    @Override\n    public UserDetails loadUserByUsername(String s) throws UsernameNotFoundException {\n        String password = mapper.getPasswordByUsername(s);  \u002F\u002F从数据库根据用户名获取密码\n        if(password == null)\n            throw new UsernameNotFoundException(\"登录失败，用户名或密码错误！\");\n        return User   \u002F\u002F这里需要返回UserDetails，SpringSecurity会根据给定的信息进行比对\n                .withUsername(s)\n                .password(password)   \u002F\u002F直接从数据库取的密码\n                .roles(\"user\")   \u002F\u002F用户角色\n                .build();\n    }\n}\n```\n\n别忘了在配置类中进行扫描，将其注册为Bean，接着我们需要编写一个Mapper用于和数据库交互：\n\n```java\n@Mapper\npublic interface UserMapper {\n\n    @Select(\"select password from users where username = #{username}\")\n    String getPasswordByUsername(String username);\n}\n```\n\n和之前一样，配置一下Mybatis和数据源：\n\n```java\n@ComponentScans({\n        @ComponentScan(\"book.manager.service\")\n})\n@MapperScan(\"book.manager.mapper\")\n@Configuration\npublic class RootConfiguration {\n    @Bean\n    public DataSource dataSource(){\n        HikariDataSource dataSource = new HikariDataSource();\n        dataSource.setJdbcUrl(\"jdbc:mysql:\u002F\u002Flocalhost:3306\u002Fstudy\");\n        dataSource.setDriverClassName(\"com.mysql.cj.jdbc.Driver\");\n        dataSource.setUsername(\"root\");\n        dataSource.setPassword(\"123456\");\n        return dataSource;\n    }\n\n    @Bean\n    public SqlSessionFactoryBean sqlSessionFactoryBean(@Autowired DataSource dataSource){\n        SqlSessionFactoryBean bean = new SqlSessionFactoryBean();\n        bean.setDataSource(dataSource);\n        return bean;\n    }\n}\n```\n\n最后再修改一下Security配置：\n\n```java\n@Override\nprotected void configure(AuthenticationManagerBuilder auth) throws Exception {\n    auth\n      .userDetailsService(service)   \u002F\u002F使用自定义的Service实现类进行验证\n      .passwordEncoder(new BCryptPasswordEncoder());   \u002F\u002F依然使用BCryptPasswordEncoder\n}\n```\n\n这样，登陆就会从数据库中进行查询。\n\n### 自定义登录界面\n\n前面我们已经了解了如何实现数据库权限验证，那么现在我们接着来看看，如何将登陆页面修改为我们自定义的样式。\n\n首先我们要了解一下SpringSecurity是如何进行登陆验证的，我们可以观察一下默认的登陆界面中，表单内有哪些内容：\n\n```html\n\u003Cdiv class=\"container\">\n      \u003Cform class=\"form-signin\" method=\"post\" action=\"\u002Fbook_manager\u002Flogin\">\n        \u003Ch2 class=\"form-signin-heading\">Please sign in\u003C\u002Fh2>\n        \u003Cp>\n          \u003Clabel for=\"username\" class=\"sr-only\">Username\u003C\u002Flabel>\n          \u003Cinput type=\"text\" id=\"username\" name=\"username\" class=\"form-control\" placeholder=\"Username\" required=\"\" autofocus=\"\">\n        \u003C\u002Fp>\n        \u003Cp>\n          \u003Clabel for=\"password\" class=\"sr-only\">Password\u003C\u002Flabel>\n          \u003Cinput type=\"password\" id=\"password\" name=\"password\" class=\"form-control\" placeholder=\"Password\" required=\"\">\n        \u003C\u002Fp>\n\u003Cinput name=\"_csrf\" type=\"hidden\" value=\"83421936-b84b-44e3-be47-58bb2c14571a\">\n        \u003Cbutton class=\"btn btn-lg btn-primary btn-block\" type=\"submit\">Sign in\u003C\u002Fbutton>\n      \u003C\u002Fform>\n\u003C\u002Fdiv>\n```\n\n我们发现，首先有一个用户名的输入框和一个密码的输入框，我们需要在其中填写用户名和密码，但是我们发现，除了这两个输入框以外，还有一个input标签，它是隐藏的，并且它存储了一串类似于Hash值的东西，名称为\"_csrf\"，其实看名字就知道，这玩意八成都是为了防止CSRF攻击而存在的。\n\n从Spring Security 4.0开始，默认情况下会启用CSRF保护，以防止CSRF攻击应用程序，Spring Security CSRF会针对PATCH，POST，PUT和DELETE方法的请求（不仅仅只是登陆请求，这里指的是任何请求路径）进行防护，而这里的登陆表单正好是一个POST类型的请求。在默认配置下，无论是否登陆，页面中只要发起了PATCH，POST，PUT和DELETE请求一定会被拒绝，并返回**403**错误**（注意，这里是个究极大坑）**，需要在请求的时候加入csrfToken才行，也就是\"83421936-b84b-44e3-be47-58bb2c14571a\"，正是csrfToken，如果提交的是表单类型的数据，那么表单中必须包含此Token字符串，键名称为\"_csrf\"；如果是JSON数据格式发送的，那么就需要在请求头中包含此Token字符串。\n\n综上所述，我们最后提交的登陆表单，除了必须的用户名和密码，还包含了一个csrfToken字符串用于验证，防止攻击。\n\n因此，我们在编写自己的登陆页面时，需要添加这样一个输入框：\n\n```html\n\u003Cinput type=\"text\" th:name=\"${_csrf.getParameterName()}\" th:value=\"${_csrf.token}\" hidden>\n```\n\n隐藏即可，但是必须要有，而Token的键名称和Token字符串可以通过Thymeleaf从Model中获取，SpringSecurity会自动将Token信息添加到Model中。\n\n接着我们就可以将我们自己的页面替换掉默认的页面了，我们需要重写另一个方法来实现：\n\n```java\n@Override\nprotected void configure(HttpSecurity http) throws Exception {\n    http\n            .authorizeRequests()   \u002F\u002F首先需要配置哪些请求会被拦截，哪些请求必须具有什么角色才能访问\n            .antMatchers(\"\u002Fstatic\u002F**\").permitAll()    \u002F\u002F静态资源，使用permitAll来运行任何人访问（注意一定要放在前面）\n            .antMatchers(\"\u002F**\").hasRole(\"user\")     \u002F\u002F所有请求必须登陆并且是user角色才可以访问（不包含上面的静态资源）\n}\n```\n\n首先我们需要配置拦截规则，也就是当用户未登录时，哪些路径可以访问，哪些路径不可以访问，如果不可以访问，那么会被自动重定向到登陆页面。\n\n接着我们需要配置表单登陆和登录页面：\n\n```java\n.formLogin()       \u002F\u002F配置Form表单登陆\n.loginPage(\"\u002Flogin\")       \u002F\u002F登陆页面地址（GET）\n.loginProcessingUrl(\"\u002FdoLogin\")    \u002F\u002Fform表单提交地址（POST）\n.defaultSuccessUrl(\"\u002Findex\")    \u002F\u002F登陆成功后跳转的页面，也可以通过Handler实现高度自定义\n.permitAll()    \u002F\u002F登陆页面也需要允许所有人访问\n```\n\n需要配置登陆页面的地址和登陆请求发送的地址，这里登陆页面填写为`\u002Flogin`，登陆请求地址为`\u002FdoLogin`，登陆页面需要我们自己去编写Controller来实现，登陆请求提交处理由SpringSecurity提供，只需要写路径就可以了。\n\n```java\n@RequestMapping(\"\u002Flogin\")\npublic String login(){\n    return \"login\";\n}\n```\n\n配置好后，我们还需要配置一下退出登陆操作：\n\n```java\n.and()\n.logout()\n.logoutUrl(\"\u002Flogout\")    \u002F\u002F退出登陆的请求地址\n.logoutSuccessUrl(\"\u002Flogin\");    \u002F\u002F退出后重定向的地址\n```\n\n注意这里的退出登陆请求也必须是POST请求方式（因为开启了CSFR防护，需要添加Token），否则无法访问，这里主页面就这样写：\n\n```html\n\u003Cbody>\n    \u003Cform action=\"logout\" method=\"post\">\n        \u003Cinput type=\"text\" th:name=\"${_csrf.getParameterName()}\" th:value=\"${_csrf.token}\" hidden>\n        \u003Cbutton>退出登陆\u003C\u002Fbutton>\n    \u003C\u002Fform>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n登陆成功后，点击退出登陆按钮，就可以成功退出并回到登陆界面了。\n\n由于我们在学习的过程中暂时用不到CSFR防护，因此可以将其关闭，这样直接使用get请求也可以退出登陆，并且登陆请求中无需再携带Token了，推荐关闭，因为不关闭后面可能会因为没考虑CSRF防护而遇到一连串的问题：\n\n```java\n.and()\n.csrf().disable();\n```\n\n这样就可以直接关闭此功能了，但是注意，这样将会导致您的Web网站存在安全漏洞。（这里为了之后省事，就关闭保护了，但是一定要记得在不关闭的情况下需要携带Token访问）\n\n***\n\n## 授权\n\n用户登录后，可能会根据用户当前是身份进行角色划分，比如我们最常用的QQ，一个QQ群里面，有群主、管理员和普通群成员三种角色，其中群主具有最高权限，群主可以管理整个群的任何板块，并且具有解散和升级群的资格，而管理员只有群主的一部分权限，只能用于日常管理，普通群成员则只能进行最基本的聊天操作。\n\n对于我们来说，用户的一个操作实际上就是在访问我们提供的`接口`(编写的对应访问路径的Servlet），比如登陆，就需要调用`\u002Flogin`接口，退出登陆就要调用\u002F`logout`接口，而我们之前的图书管理系统中，新增图书、删除图书，所有的操作都有着对应的Servlet来进行处理。因此，从我们开发者的角度来说，决定用户能否使用某个功能，只需要决定用户是否能够访问对应的Servlet即可。\n\n我们可以大致像下面这样进行划分：\n\n* 群主：`\u002Flogin`、`\u002Flogout`、`\u002Fchat`、`\u002Fedit`、`\u002Fdelete`、`\u002Fupgrade`\n* 管理员：`\u002Flogin`、`\u002Flogout`、`\u002Fchat`、`\u002Fedit`\n* 普通群成员：`\u002Flogin`、`\u002Flogout`、`\u002Fchat`\n\n也就是说，我们需要做的就是指定哪些请求可以由哪些用户发起。\n\nSpringSecurity为我们提供了两种授权方式：\n\n* 基于权限的授权：只要拥有某权限的用户，就可以访问某个路径\n* 基于角色的授权：根据用户属于哪个角色来决定是否可以访问某个路径\n\n两者只是概念上的不同，实际上使用起来效果差不多。这里我们就先演示以角色方式来进行授权。\n\n### 基于角色的授权\n\n现在我们希望创建两个角色，普通用户和管理员，普通用户只能访问index页面，而管理员可以访问任何页面。\n\n首先我们需要对数据库中的角色表进行一些修改，添加一个用户角色字段，并创建一个新的用户，Test用户的角色为user，而Admin用户的角色为admin。\n\n接着我们需要配置SpringSecurity，决定哪些角色可以访问哪些页面：\n\n```java\nhttp\n        .authorizeRequests()\n        .antMatchers(\"\u002Fstatic\u002F**\").permitAll()\n  \t\t\t.antMatchers(\"\u002Findex\").hasAnyRole(\"user\", \"admin\")   \u002F\u002Findex页面可以由user或admin访问\n        .anyRequest().hasRole(\"admin\")   \u002F\u002F除了上面以外的所有内容，只能是admin访问\n```\n\n接着我们需要稍微修改一下验证逻辑，首先创建一个实体类用于表示数据库中的用户名、密码和角色：\n\n```java\n@Data\npublic class AuthUser {\n    String username;\n    String password;\n    String role;\n}\n```\n\n接着修改一下Mapper：\n\n```java\n@Mapper\npublic interface UserMapper {\n\n    @Select(\"select * from users where username = #{username}\")\n    AuthUser getPasswordByUsername(String username);\n}\n```\n\n最后再修改一下Service：\n\n```java\n@Override\npublic UserDetails loadUserByUsername(String s) throws UsernameNotFoundException {\n    AuthUser user = mapper.getPasswordByUsername(s);\n    if(user == null)\n        throw new UsernameNotFoundException(\"登录失败，用户名或密码错误！\");\n    return User\n            .withUsername(user.getUsername())\n            .password(user.getPassword())\n            .roles(user.getRole())\n            .build();\n}\n```\n\n现在我们可以尝试登陆，接着访问一下`\u002Findex`和`\u002Fadmin`两个页面。\n\n### 基于权限的授权\n\n基于权限的授权与角色类似，需要以`hasAnyAuthority`或`hasAuthority`进行判断：\n\n```java\n.anyRequest().hasAnyAuthority(\"page:index\")\n```\n\n```java\n@Override\npublic UserDetails loadUserByUsername(String s) throws UsernameNotFoundException {\n    AuthUser user = mapper.getPasswordByUsername(s);\n    if(user == null)\n        throw new UsernameNotFoundException(\"登录失败，用户名或密码错误！\");\n    return User\n            .withUsername(user.getUsername())\n            .password(user.getPassword())\n            .authorities(\"page:index\")\n            .build();\n}\n```\n\n### 使用注解判断权限\n\n除了直接配置以外，我们还可以以注解形式直接配置，首先需要在配置类（注意这里是在Mvc的配置类上添加，因为这里只针对Controller进行过滤，所有的Controller是由Mvc配置类进行注册的，如果需要为Service或其他Bean也启用权限判断，则需要在Security的配置类上添加）上开启：\n\n```java\n@EnableGlobalMethodSecurity(prePostEnabled = true)\npublic class SecurityConfiguration extends WebSecurityConfigurerAdapter {\n```\n\n接着我们可以直接在需要添加权限验证的请求映射上添加注解：\n\n```java\n@PreAuthorize(\"hasRole('user')\")   \u002F\u002F判断是否为user角色，只有此角色才可以访问\n@RequestMapping(\"\u002Findex\")\npublic String index(){\n    return \"index\";\n}\n```\n\n通过添加`@PreAuthorize`注解，在执行之前判断判断权限，如果没有对应的权限或是对应的角色，将无法访问页面。\n\n这里其实是使用了SpEL表达式，相当于可以执行一些逻辑再得到结果，而不是直接传值，官方文档地址：https:\u002F\u002Fdocs.spring.io\u002Fspring-framework\u002Fdocs\u002F5.2.13.RELEASE\u002Fspring-framework-reference\u002Fcore.html#expressions，内容比较多，不是重点，这里就不再详细介绍了。\n\n同样的还有`@PostAuthorize`注解，但是它是在方法执行之后再进行拦截：\n\n```java\n@PostAuthorize(\"hasRole('user')\")\n@RequestMapping(\"\u002Findex\")\npublic String index(){\n    System.out.println(\"执行了\");\n    return \"index\";\n}\n```\n\n除了Controller以外，只要是由Spring管理的Bean都可以使用注解形式来控制权限，只要不具备访问权限，那么就无法执行方法并且会返回403页面。\n\n```java\n@Service\npublic class UserService {\n\n    @PreAuthorize(\"hasAnyRole('user')\")\n    public void test(){\n        System.out.println(\"成功执行\");\n    }\n}\n```\n\n注意Service是由根容器进行注册，需要在Security配置类上添加`@EnableGlobalMethodSecurity`注解才可以生效。与具有相同功能的还有`@Secure`但是它不支持SpEL表达式的权限表示形式，并且需要添加\"ROLE_\"前缀，这里就不做演示了。\n\n我们还可以使用`@PreFilter`和`@PostFilter`对集合类型的参数或返回值进行过滤。\n\n比如：\n\n```java\n@PreFilter(\"filterObject.equals('lbwnb')\")   \u002F\u002FfilterObject代表集合中每个元素，只要满足条件的元素才会留下\npublic void test(List\u003CString> list){\n    System.out.println(\"成功执行\"+list);\n}\n```\n\n```java\n@RequestMapping(\"\u002Findex\")\npublic String index(){\n    List\u003CString> list = new LinkedList\u003C>();\n    list.add(\"lbwnb\");\n    list.add(\"yyds\");\n    service.test(list);\n    return \"index\";\n}\n```\n\n与`@PreFilter`类似的`@PostFilter`这里就不做演示了，它用于处理返回值，使用方法是一样的。\n\n当有多个集合时，需要使用`filterTarget`进行指定：\n\n```java\n@PreFilter(value = \"filterObject.equals('lbwnb')\", filterTarget = \"list2\")\npublic void test(List\u003CString> list, List\u003CString> list2){\n    System.out.println(\"成功执行\"+list);\n}\n```\n\n***\n\n## 记住我\n\n我们的网站还有一个重要的功能，就是记住我，也就是说我们可以在登陆之后的一段时间内，无需再次输入账号和密码进行登陆，相当于服务端已经记住当前用户，再次访问时就可以免登陆进入，这是一个非常常用的功能。\n\n我们之前在JavaWeb阶段，使用本地Cookie存储的方式实现了记住我功能，但是这种方式并不安全，同时在代码编写上也比较麻烦，那么能否有一种更加高效的记住我功能实现呢？\n\nSpringSecurity为我们提供了一种优秀的实现，它为每个已经登陆的浏览器分配一个携带Token的Cookie，并且此Cookie默认会被保留14天，只要我们不清理浏览器的Cookie，那么下次携带此Cookie访问服务器将无需登陆，直接继续使用之前登陆的身份，这样显然比我们之前的写法更加简便。并且我们需要进行简单配置，即可开启记住我功能：\n\n```java\n.and()\n.rememberMe()   \u002F\u002F开启记住我功能\n.rememberMeParameter(\"remember\")  \u002F\u002F登陆请求表单中需要携带的参数，如果携带，那么本次登陆会被记住\n.tokenRepository(new InMemoryTokenRepositoryImpl())  \u002F\u002F这里使用的是直接在内存中保存的TokenRepository实现\n  \u002F\u002FTokenRepository有很多种实现，InMemoryTokenRepositoryImpl直接基于Map实现的，缺点就是占内存、服务器重启后记住我功能将失效\n  \u002F\u002F后面我们还会讲解如何使用数据库来持久化保存Token信息\n```\n\n接着我们需要在前端修改一下记住我勾选框的名称，将名称修改与上面一致，如果上面没有配置名称，那么默认使用\"remember-me\"作为名称：\n\n```html\n\u003Cinput type=\"checkbox\" name=\"remember\" class=\"ad-checkbox\">\n```\n\n现在我们启动服务器，在登陆时勾选记住我勾选框，观察Cookie的变化。\n\n虽然现在已经可以实现记住我功能了，但是还有一定的缺陷，如果服务器重新启动（因为Token信息全部存在HashMap中，也就是存在内存中），那么所有记录的Token信息将全部丢失，这时即使浏览器携带了之前的Token也无法恢复之前登陆的身份。\n\n我们可以将Token信息记录全部存放到数据库中（学习了Redis之后还可以放到Redis服务器中）利用数据库的持久化存储机制，即使服务器重新启动，所有的Token信息也不会丢失，配置数据库存储也很简单：\n\n```java\n@Resource\nPersistentTokenRepository repository;\n\n@Bean\npublic PersistentTokenRepository jdbcRepository(@Autowired DataSource dataSource){\n    JdbcTokenRepositoryImpl repository = new JdbcTokenRepositoryImpl();  \u002F\u002F使用基于JDBC的实现\n    repository.setDataSource(dataSource);   \u002F\u002F配置数据源\n  \trepository.setCreateTableOnStartup(true);   \u002F\u002F启动时自动创建用于存储Token的表（建议第一次启动之后删除该行）\n    return repository;\n}\n```\n\n```java\n.and()\n.rememberMe()\n.rememberMeParameter(\"remember\")\n.tokenRepository(repository)\n.tokenValiditySeconds(60 * 60 * 24 * 7)  \u002F\u002FToken的有效时间（秒）默认为14天\n```\n\n稍后服务器启动我们可以观察一下数据库，如果出现名为`persistent_logins`的表，那么证明配置没有问题。\n\n当我们登陆并勾选了记住我之后，那么数据库中会新增一条Token记录。\n\n***\n\n## SecurityContext\n\n用户登录之后，怎么获取当前已经登录用户的信息呢？通过使用SecurityContextHolder就可以很方便地得到SecurityContext对象了，我们可以直接使用SecurityContext对象来获取当前的认证信息：\n\n```java\n@RequestMapping(\"\u002Findex\")\n    public String index(){\n        SecurityContext context = SecurityContextHolder.getContext();\n        Authentication authentication = context.getAuthentication();\n        User user = (User) authentication.getPrincipal();\n        System.out.println(user.getUsername());\n        System.out.println(user.getAuthorities());\n        return \"index\";\n    }\n```\n\n通过SecurityContext我们就可以快速获取当前用户的名称和授权信息等。\n\n除了这种方式以外，我们还可以直接从Session中获取：\n\n```java\n@RequestMapping(\"\u002Findex\")\npublic String index(@SessionAttribute(\"SPRING_SECURITY_CONTEXT\") SecurityContext context){\n    Authentication authentication = context.getAuthentication();\n    User user = (User) authentication.getPrincipal();\n    System.out.println(user.getUsername());\n    System.out.println(user.getAuthorities());\n    return \"index\";\n}\n```\n\n注意SecurityContextHolder是有一定的存储策略的，SecurityContextHolder中的SecurityContext对象会在一开始请求到来时被设定，至于存储方式其实是由存储策略决定的，如果我们这样编写，那么在默认情况下是无法获取到认证信息的：\n\n```java\n@RequestMapping(\"\u002Findex\")\npublic String index(){\n    new Thread(() -> {   \u002F\u002F创建一个子线程去获取\n        SecurityContext context = SecurityContextHolder.getContext();\n        Authentication authentication = context.getAuthentication();\n        User user = (User) authentication.getPrincipal();   \u002F\u002FNPE\n        System.out.println(user.getUsername());\n        System.out.println(user.getAuthorities()); \n    });\n    return \"index\";\n}\n```\n\n这是因为SecurityContextHolder的存储策略默认是`MODE_THREADLOCAL`，它是基于ThreadLocal实现的，`getContext()`方法本质上调用的是对应的存储策略实现的方法：\n\n```java\npublic static SecurityContext getContext() {\n    return strategy.getContext();\n}\n```\n\nSecurityContextHolderStrategy有三个实现类：\n\n* GlobalSecurityContextHolderStrategy：全局模式，不常用\n* ThreadLocalSecurityContextHolderStrategy：基于ThreadLocal实现，线程内可见\n* InheritableThreadLocalSecurityContextHolderStrategy：基于InheritableThreadLocal实现，线程和子线程可见\n\n因此，如果上述情况需要在子线程中获取，那么需要修改SecurityContextHolder的存储策略，在初始化的时候设置：\n\n```java\n@PostConstruct\npublic void init(){\n    SecurityContextHolder.setStrategyName(SecurityContextHolder.MODE_INHERITABLETHREADLOCAL);\n}\n```\n\n这样在子线程中也可以获取认证信息了。\n\n因为用户的验证信息是基于SecurityContext进行判断的，我们可以直接修改SecurityContext的内容，来手动为用户进行登陆：\n\n```java\n@RequestMapping(\"\u002Fauth\")\n@ResponseBody\npublic String auth(){\n    SecurityContext context = SecurityContextHolder.getContext();  \u002F\u002F获取SecurityContext对象（当前会话肯定是没有登陆的）\n    UsernamePasswordAuthenticationToken token = new UsernamePasswordAuthenticationToken(\"Test\", null,\n            AuthorityUtils.commaSeparatedStringToAuthorityList(\"ROLE_user\"));  \u002F\u002F手动创建一个UsernamePasswordAuthenticationToken对象，也就是用户的认证信息，角色需要添加ROLE_前缀，权限直接写\n    context.setAuthentication(token);  \u002F\u002F手动为SecurityContext设定认证信息\n    return \"Login success！\";\n}\n```\n\n在未登陆的情况下，访问此地址将直接进行手动登陆，再次访问`\u002Findex`页面，可以直接访问，说明手动设置认证信息成功。\n\n**疑惑：** SecurityContext这玩意不是默认线程独占吗，那每次请求都是一个新的线程，按理说上一次的SecurityContext对象应该没了才对啊，为什么再次请求依然能够继续使用上一次SecurityContext中的认证信息呢？\n\nSecurityContext的生命周期：请求到来时从Session中取出，放入SecurityContextHolder中，请求结束时从SecurityContextHolder取出，并放到Session中，实际上就是依靠Session来存储的，一旦会话过期验证信息也跟着消失。\n\n***\n\n## SpringSecurity原理\n\n**注意：** 本小节内容作为选学内容，但是难度比前两章的源码部分简单得多。\n\n最后我们再来聊一下SpringSecurity的实现原理，它本质上是依靠N个Filter实现的，也就是一个完整的过滤链（注意这里是过滤器，不是拦截器）\n\n我们就从`AbstractSecurityWebApplicationInitializer`开始下手，我们来看看它配置了什么：\n\n```java\n\u002F\u002F此方法会在启动时被调用\npublic final void onStartup(ServletContext servletContext) {\n    this.beforeSpringSecurityFilterChain(servletContext);\n    if (this.configurationClasses != null) {\n        AnnotationConfigWebApplicationContext rootAppContext = new AnnotationConfigWebApplicationContext();\n        rootAppContext.register(this.configurationClasses);\n        servletContext.addListener(new ContextLoaderListener(rootAppContext));\n    }\n\n    if (this.enableHttpSessionEventPublisher()) {\n        servletContext.addListener(\"org.springframework.security.web.session.HttpSessionEventPublisher\");\n    }\n\n    servletContext.setSessionTrackingModes(this.getSessionTrackingModes());\n  \t\u002F\u002F重点在这里，这里插入了关键的FilterChain\n    this.insertSpringSecurityFilterChain(servletContext);\n    this.afterSpringSecurityFilterChain(servletContext);\n}\n```\n\n```java\nprivate void insertSpringSecurityFilterChain(ServletContext servletContext) {\n    String filterName = \"springSecurityFilterChain\";\n  \t\u002F\u002F创建了一个DelegatingFilterProxy对象，它本质上也是一个Filter\n    DelegatingFilterProxy springSecurityFilterChain = new DelegatingFilterProxy(filterName);\n    String contextAttribute = this.getWebApplicationContextAttribute();\n    if (contextAttribute != null) {\n        springSecurityFilterChain.setContextAttribute(contextAttribute);\n    }\n\t\t\u002F\u002F通过ServletContext注册DelegatingFilterProxy这个Filter\n    this.registerFilter(servletContext, true, filterName, springSecurityFilterChain);\n}\n```\n\n我们接着来看看，`DelegatingFilterProxy`在做什么：\n\n```java\n\u002F\u002F这个是初始化方法，它由GenericFilterBean（父类）定义，在afterPropertiesSet方法中被调用\nprotected void initFilterBean() throws ServletException {\n    synchronized(this.delegateMonitor) {\n        if (this.delegate == null) {\n            if (this.targetBeanName == null) {\n                this.targetBeanName = this.getFilterName();\n            }\n\n            WebApplicationContext wac = this.findWebApplicationContext();\n            if (wac != null) {\n              \t\u002F\u002F耐心点，套娃很正常\n                this.delegate = this.initDelegate(wac);\n            }\n        }\n\n    }\n}\n```\n\n```java\nprotected Filter initDelegate(WebApplicationContext wac) throws ServletException {\n    String targetBeanName = this.getTargetBeanName();\n    Assert.state(targetBeanName != null, \"No target bean name set\");\n  \t\u002F\u002F这里通过WebApplicationContext获取了一个Bean\n    Filter delegate = (Filter)wac.getBean(targetBeanName, Filter.class);\n    if (this.isTargetFilterLifecycle()) {\n        delegate.init(this.getFilterConfig());\n    }\n\n  \t\u002F\u002F返回Filter\n    return delegate;\n}\n```\n\n这里我们需要添加一个断点来查看到底获取到了什么Bean。\n\n通过断点调试，我们发现这里放回的对象是一个FilterChainProxy类型的，并且调用了它的初始化方法，但是FilterChainProxy类中并没有重写`init`方法或是`initFilterBean`方法。\n\n我们倒回去看，当Filter返回之后，`DelegatingFilterProxy`的一个成员变量`delegate`被赋值为得到的Filter，也就是FilterChainProxy对象，接着我们来看看，`DelegatingFilterProxy`是如何执行doFilter方法的。\n\n```java\npublic void doFilter(ServletRequest request, ServletResponse response, FilterChain filterChain) throws ServletException, IOException {\n    Filter delegateToUse = this.delegate;\n    if (delegateToUse == null) {\n        \u002F\u002F非正常情况，这里省略...\n    }\n\t\t\u002F\u002F这里才是真正的调用，别忘了delegateToUse就是初始化的FilterChainProxy对象\n    this.invokeDelegate(delegateToUse, request, response, filterChain);\n}\n```\n\n```java\nprotected void invokeDelegate(Filter delegate, ServletRequest request, ServletResponse response, FilterChain filterChain) throws ServletException, IOException {\n  \u002F\u002F最后实际上调用的是FilterChainProxy的doFilter方法\n    delegate.doFilter(request, response, filterChain);\n}\n```\n\n所以我们接着来看，`FilterChainProxy`的doFilter方法又在干什么：\n\n```java\npublic void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {\n    boolean clearContext = request.getAttribute(FILTER_APPLIED) == null;\n    if (!clearContext) {\n      \t\u002F\u002F真正的过滤在这里执行\n        this.doFilterInternal(request, response, chain);\n    } else {\n        \u002F\u002F...\n    }\n}\n```\n\n```java\nprivate void doFilterInternal(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {\n    FirewalledRequest firewallRequest = this.firewall.getFirewalledRequest((HttpServletRequest)request);\n    HttpServletResponse firewallResponse = this.firewall.getFirewalledResponse((HttpServletResponse)response);\n  \t\u002F\u002F这里获取了一个Filter列表，实际上SpringSecurity就是由N个过滤器实现的，这里获取的都是SpringSecurity提供的过滤器\n  \t\u002F\u002F但是请注意，经过我们之前的分析，实际上真正注册的Filter只有DelegatingFilterProxy\n  \t\u002F\u002F而这里的Filter列表中的所有Filter并没有被注册，而是在这里进行内部调用\n    List\u003CFilter> filters = this.getFilters((HttpServletRequest)firewallRequest);\n  \t\u002F\u002F只要Filter列表不是空，就依次执行内置的Filter\n    if (filters != null && filters.size() != 0) {\n        if (logger.isDebugEnabled()) {\n            logger.debug(LogMessage.of(() -> {\n                return \"Securing \" + requestLine(firewallRequest);\n            }));\n        }\n\t\t\t\t\u002F\u002F这里创建一个虚拟的过滤链，过滤流程是由SpringSecurity自己实现的\n        FilterChainProxy.VirtualFilterChain virtualFilterChain = new FilterChainProxy.VirtualFilterChain(firewallRequest, chain, filters);\n      \t\u002F\u002F调用虚拟过滤链的doFilter\n        virtualFilterChain.doFilter(firewallRequest, firewallResponse);\n    } else {\n        if (logger.isTraceEnabled()) {\n            logger.trace(LogMessage.of(() -> {\n                return \"No security for \" + requestLine(firewallRequest);\n            }));\n        }\n\n        firewallRequest.reset();\n        chain.doFilter(firewallRequest, firewallResponse);\n    }\n}\n```\n\n我们来看一下虚拟过滤链的doFilter是怎么处理的：\n\n```java\n\u002F\u002F看似没有任何循环，实际上就是一个循环，是一个递归调用\npublic void doFilter(ServletRequest request, ServletResponse response) throws IOException, ServletException {\n  \t\u002F\u002F判断是否已经通过全部的内置过滤器，定位是否等于当前大小\n    if (this.currentPosition == this.size) {\n        if (FilterChainProxy.logger.isDebugEnabled()) {\n            FilterChainProxy.logger.debug(LogMessage.of(() -> {\n                return \"Secured \" + FilterChainProxy.requestLine(this.firewalledRequest);\n            }));\n        }\n\n        this.firewalledRequest.reset();\n      \t\u002F\u002F所有的内置过滤器已经完成，按照正常流程走DelegatingFilterProxy的下一个Filter\n      \t\u002F\u002F也就是说这里之后就与DelegatingFilterProxy没有任何关系了，该走其他过滤器就走其他地方配置的过滤器，SpringSecurity的过滤操作已经结束\n        this.originalChain.doFilter(request, response);\n    } else {\n      \t\u002F\u002F定位自增\n        ++this.currentPosition;\n      \t\u002F\u002F获取当前定位的Filter\n        Filter nextFilter = (Filter)this.additionalFilters.get(this.currentPosition - 1);\n        if (FilterChainProxy.logger.isTraceEnabled()) {\n            FilterChainProxy.logger.trace(LogMessage.format(\"Invoking %s (%d\u002F%d)\", nextFilter.getClass().getSimpleName(), this.currentPosition, this.size));\n        }\n\t\t\t\t\u002F\u002F执行内部过滤器的doFilter方法，传入当前对象本身作为Filter，执行如果成功，那么一定会再次调用当前对象的doFilter方法\n      \t\u002F\u002F可能最不理解的就是这里，执行的难道不是内部其他Filter的doFilter方法吗，怎么会让当前对象的doFilter方法递归调用呢？\n      \t\u002F\u002F没关系，了解了其中一个内部过滤器就明白了\n        nextFilter.doFilter(request, response, this);\n    }\n}\n```\n\n因此，我们差不多已经了解了整个SpringSecurity的实现机制了，那么我们来看几个内部的过滤器分别在做什么。\n\n比如用于处理登陆的过滤器`UsernamePasswordAuthenticationFilter`，它继承自`AbstractAuthenticationProcessingFilter`，我们来看看它是怎么进行过滤的：\n\n```java\npublic void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {\n    this.doFilter((HttpServletRequest)request, (HttpServletResponse)response, chain);\n}\n\nprivate void doFilter(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws IOException, ServletException {\n  \t\u002F\u002F如果不是登陆请求，那么根本不会理这个请求\n    if (!this.requiresAuthentication(request, response)) {\n      \t\u002F\u002F直接调用传入的FilterChain的doFilter方法\n      \t\u002F\u002F而这里传入的正好是VirtualFilterChain对象\n      \t\u002F\u002F这下知道为什么上面说是递归了吧\n        chain.doFilter(request, response);\n    } else {\n      \t\u002F\u002F如果是登陆请求，那么会执行登陆请求的相关逻辑，注意执行过程中出现任何问题都会抛出异常\n      \t\u002F\u002F比如用户名和密码错误，我们之前也已经测试过了，会得到一个BadCredentialsException\n        try {\n          \t\u002F\u002F进行认证\n            Authentication authenticationResult = this.attemptAuthentication(request, response);\n            if (authenticationResult == null) {\n                return;\n            }\n\n            this.sessionStrategy.onAuthentication(authenticationResult, request, response);\n            if (this.continueChainBeforeSuccessfulAuthentication) {\n                chain.doFilter(request, response);\n            }\n\n          \t\u002F\u002F如果一路绿灯，没有报错，那么验证成功，执行successfulAuthentication\n            this.successfulAuthentication(request, response, chain, authenticationResult);\n        } catch (InternalAuthenticationServiceException var5) {\n            this.logger.error(\"An internal error occurred while trying to authenticate the user.\", var5);\n          \t\u002F\u002F验证失败，会执行unsuccessfulAuthentication\n            this.unsuccessfulAuthentication(request, response, var5);\n        } catch (AuthenticationException var6) {\n            this.unsuccessfulAuthentication(request, response, var6);\n        }\n\n    }\n}\n```\n\n那么我们来看看successfulAuthentication和unsuccessfulAuthentication分别做了什么：\n\n```java\nprotected void successfulAuthentication(HttpServletRequest request, HttpServletResponse response, FilterChain chain, Authentication authResult) throws IOException, ServletException {\n  \t\u002F\u002F向SecurityContextHolder添加认证信息，我们可以通过SecurityContextHolder对象获取当前登陆的用户\n    SecurityContextHolder.getContext().setAuthentication(authResult);\n    if (this.logger.isDebugEnabled()) {\n        this.logger.debug(LogMessage.format(\"Set SecurityContextHolder to %s\", authResult));\n    }\n\n  \t\u002F\u002F记住我实现\n    this.rememberMeServices.loginSuccess(request, response, authResult);\n    if (this.eventPublisher != null) {\n        this.eventPublisher.publishEvent(new InteractiveAuthenticationSuccessEvent(authResult, this.getClass()));\n    }\n\t\t\n  \t\u002F\u002F调用默认的或是我们自己定义的AuthenticationSuccessHandler的onAuthenticationSuccess方法\n  \t\u002F\u002F这个根据我们配置文件决定\n  \t\u002F\u002F到这里其实页面就已经直接跳转了\n    this.successHandler.onAuthenticationSuccess(request, response, authResult);\n}\n\nprotected void unsuccessfulAuthentication(HttpServletRequest request, HttpServletResponse response, AuthenticationException failed) throws IOException, ServletException {\n  \t\u002F\u002F登陆失败会直接清理掉SecurityContextHolder中的认证信息\n    SecurityContextHolder.clearContext();\n    this.logger.trace(\"Failed to process authentication request\", failed);\n    this.logger.trace(\"Cleared SecurityContextHolder\");\n    this.logger.trace(\"Handling authentication failure\");\n  \t\u002F\u002F登陆失败的记住我处理\n    this.rememberMeServices.loginFail(request, response);\n  \t\u002F\u002F同上，调用默认或是我们自己定义的AuthenticationFailureHandler\n    this.failureHandler.onAuthenticationFailure(request, response, failed);\n}\n```\n\n了解了整个用户验证实现流程，其实其它的过滤器是如何实现的也就很容易联想到了，SpringSecurity的过滤器从某种意义上来说，更像是一个处理业务的Servlet，它做的事情不像是拦截，更像是完成自己对应的职责，只不过是使用了过滤器机制进行实现罢了。\n\nSecurityContextPersistenceFilter也是内置的Filter，可以尝试阅读一下其源码，了解整个SecurityContextHolder的运作原理，这里先说一下大致流程，各位可以依照整个流程按照源码进行推导：\n\n当过滤器链执行到SecurityContextPersistenceFilter时，它会从HttpSession中把SecurityContext对象取出来（是存在Session中的，跟随会话的消失而消失），然后放入SecurityContextHolder对象中。请求结束后，再把SecurityContext存入HttpSession中，并清除SecurityContextHolder内的SecurityContext对象。\n\n***\n\n## 完善功能\n\n在了解了SpringSecurity的大部分功能后，我们就来将整个网站的内容进行完善，登陆目前已经实现了，我们还需要实现以下功能：\n\n* 注册功能（仅针对于学生）\n* 角色分为同学和管理员\n  * 管理员负责上架、删除、更新书籍，查看所有同学的借阅列表\n  * 同学可以借阅和归还书籍，以及查看自己的借阅列表\n\n开始之前我们需要先配置一下Thymeleaf的SpringSecurity扩展，它针对SpringSecurity提供了更多额外的解析：\n\n```xml\n\u003Cdependency>\n    \u003CgroupId>org.thymeleaf.extras\u003C\u002FgroupId>\n    \u003CartifactId>thymeleaf-extras-springsecurity5\u003C\u002FartifactId>\n    \u003Cversion>3.0.4.RELEASE\u003C\u002Fversion>\n\u003C\u002Fdependency>\n```\n\n```java\n\u002F\u002F配置模板引擎Bean\n@Bean\npublic SpringTemplateEngine springTemplateEngine(@Autowired ITemplateResolver resolver){\n    SpringTemplateEngine engine = new SpringTemplateEngine();\n    engine.setTemplateResolver(resolver);\n    engine.addDialect(new SpringSecurityDialect());   \u002F\u002F添加针对于SpringSecurity的方言\n    return engine;\n}\n```\n\n```html\n\u003Chtml lang=\"en\" xmlns:th=\"http:\u002F\u002Fwww.thymeleaf.org\"\n      xmlns:sec=\"http:\u002F\u002Fwww.thymeleaf.org\u002Fextras\u002Fspring-security\">\n```\n\n下一章就是最后一章了，我们会深入讲解MySQL的高级部分，包括函数、存储过程、锁机制、索引以及存储引擎。\n",{"data":466,"status":460,"success":461},[467,472],{"id":8,"image":468,"link":469,"name":470,"type":471},"\u002Fimage\u002Fadv\u002Frainyun-2025-06.webp","https:\u002F\u002Fwww.rainyun.com\u002Fitbaima_","雨云优惠购","cloud",{"id":66,"image":473,"link":474,"name":475,"type":476},"\u002Fimage\u002Fadv\u002Fsimcard-2025-11.webp","https:\u002F\u002Fmall.itbaima.cn","号卡优惠","simcard"]