Spring security real combat dry goods: how to build and execute oauth2 authorization request

Little fat brother manong 2020-11-11 09:26:02
spring security real combat dry


stay Spring Security Combat dry goods : client OAuth2 Access to authorization requests We found the interceptor OAuth2 Authorization request entry /oauth2/authorization Filter OAuth2AuthorizationRequestRedirectFilter, And found the real launch OAuth2 How to authorize a request sendRedirectForAuthorization. But this method does not elaborate , So today I'll go on to the last article to fill in this hole .

2. sendRedirectForAuthorization

This sendRedirectForAuthorization Methods don't have much code , Its main function is to authorize redirection access to the third-party platform . All its logic is related to OAuth2AuthorizationRequest of , So we are OAuth2AuthorizationRequest It doesn't work to understate , We have to master OAuth2AuthorizationRequest How did you get it , What is it for .

OAuth2AuthorizationRequestResolver

This requires parsing classes OAuth2AuthorizationRequestResolver, Its core approach has two overloads , It's enough to analyze one here .

@Override
public OAuth2AuthorizationRequest resolve(HttpServletRequest request) {
// registrationId It's through uri Path parameter /oauth2/authorization/{registrationId} To obtain the
String registrationId = this.resolveRegistrationId(request);
// And then ask for the object request Extract from key by action Parameters of , The default value is login
String redirectUriAction = getAction(request, "login");
// And then we go to the fundamental parsing method
return resolve(request, registrationId, redirectUriAction);
}

In the above method resolve(request, registrationId, redirectUriAction) It's the method that ultimately comes from /oauth2/authorization extract OAuth2AuthorizationRequest The fundamental method of . There's too much code, but I try to make it easy to understand .resolve Methods will be based on different authorization methods (AuthorizationGrantType) To assemble different OAuth2AuthorizationRequest.

3. OAuth2AuthorizationRequest

The next step is OAuth2.0 At the heart of the agreement , Maybe your customized reference will come from here in the future , It's about knowledge . I will be right. OAuth2AuthorizationRequestResolver Under all kinds of authorization OAuth2AuthorizationRequest Object analysis for a complete summary . It is roughly divided into the following two parts :

3.1 from AuthorizationGrantType Decisive

In different AuthorizationGrantType Next pair OAuth2AuthorizationRequest The carding of . The member variables involved are :

  • authorizationGrantType , From configuration spring.security.client.registration.{registrationId}.authorizationGrantType.
  • responseType , from authorizationGrantType Value determination of , Refer to the following JSON.
  • additionalParameters, When authorizationGrantType The value is authorization_code Some additional parameters are required , Refer to the following JSON .
  • attributes, Different authorizationGrantType There are different attributes .

It's similar to {registrationId} Formal representation of {registrationId} It's a variable , for example registrationId=gitee.

stay OAuth2 Client configuration spring.security.client.registration.{registrationId} There are five situations in the prefix of .

When scope It doesn't contain openid and client-authentication-method Not for none The four parameters mentioned above :

{
"authorizationGrantType": "authorization_code",
"responseType": "code",
"additionalParameters": {},
"attributes": {
"registration_id": "{registrationId}"
}
}

When scope contain openid and client-authentication-method Not for none The four parameters mentioned above :

{
"authorizationGrantType": "authorization_code",
"responseType": "code",
"additionalParameters": {
"nonce": "{nonce} Of Hash value "
},
"attributes": {
"registration_id": "{registrationId}",
"nonce": "{nonce}"
}
}

When scope It doesn't contain openid and client-authentication-method by none The four parameters mentioned above :

{
"authorizationGrantType": "authorization_code",
"responseType": "code",
"additionalParameters": {
"code_challenge": "{codeVerifier} Of Hash value ",
// code_challenge_method When it's not SHA256 Maybe not key
"code_challenge_method": "S256( If it is SHA256 Algorithmic words )"
},
"attributes": {
"registration_id": "{registrationId}",
"code_verifier": "Base64 Generated security {codeVerifier}"
}
}

When scope contain openid and client-authentication-method by none The four parameters mentioned above :

{
"authorizationGrantType": "authorization_code",
"responseType": "code",
"additionalParameters": {
"code_challenge": "{codeVerifier} Of Hash value ",
// code_challenge_method When it's not SHA256 Maybe not key
"code_challenge_method": "S256( If it is SHA256 Algorithmic words )",
"nonce": "{nonce} Of Hash value "
},
"attributes": {
"registration_id": "{registrationId}",
"code_verifier": "Base64 Generated security {codeVerifier}",
"nonce": "{nonce}"
}
}

implicit It's much simpler :

{
"authorizationGrantType": "implicit",
"responseType": "token",
"attributes": {}
}

3.2 Fixed rules part

It's all kinds of different AuthorizationGrantType Under the OAuth2AuthorizationRequest Personalized value strategy of member variables of , There are also several parameters whose rules are fixed :

  • clientId From configuration , It's the only identity given to us by the third party platform .
  • authorizationUri From configuration , Used to construct requests to third parties URL.
  • scopes From configuration , It's the scope that the third-party platform authorized us to delimit , It can be understood as a role .
  • state Automatically generated , In order to prevent csrf attack .
  • authorizationRequestUri Initiating authorization request to a third-party platform , You can go directly through OAuth2AuthorizationRequest To set or use the build class above authorizationUri And so on , We will analyze the structural mechanism later .
  • redirectUri When OAuth2AuthorizationRequest After being received by a third party platform , Third party platforms will call back this URI To respond to authorization requests , The mechanism will be analyzed later .

authorizationRequestUri The construction mechanism of

If you don't explicitly provide authorizationRequestUri Would pass OAuth2AuthorizationRequest Medium

  • responseType
  • clientId
  • scopes
  • state
  • redirectUri
  • additionalParameters

According to the following rules to splice into authorizationUri Parameter string of , Parameter string key and value To carry out URI code .

authorizationUri?response_type={responseType.getValue()}&client_id={clientId}&scope={scopes Element one character space }&state={state}&redirect_uri={redirectUri}&{additionalParameter Expand to do the same thing KV Parameter string }

then OAuth2AuthorizationRequestRedirectFilter Responsible for redirecting to authorizationRequestUri Request authorization from a third party .

redirectUri

When a third party receives a response, it calls redirectUri, Callback also has some default rules , It follows {baseUrl}/{action}/oauth2/code/{registrationId} The path parameter rule of .

  • baseUrl It's from us /oauth2/authorization The underlying request path extracted from the request .
  • action, There are two default values loginauthorize , When /oauth2/authorization The request contains action Parameters are based on action Fill in the value of .
  • registrationId I don't have to say much about that .

4. summary

Through to OAuth2AuthorizationRequest The rules of the request object are analyzed in detail , We should be able to roughly know the filter OAuth2AuthorizationRequestRedirectFilter technological process :

  1. Build through client configuration ClientRegistration, It can be persisted later .
  2. Intercept /oauth2/authorization Request and construct OAuth2AuthorizationRequest, And then redirect to authorizationRequestUri To request authorization .
  3. Third party adoption redirect_uri Corresponding .

that Spring Security OAuth2 How to deal with the callback of the third party ? Focus on : Small fat man of minong For you to find out the answer .

Official account :Felordcn Get more information

Personal blog :https://felord.cn

版权声明
本文为[Little fat brother manong]所创,转载请带上原文链接,感谢

  1. 【计算机网络 12(1),尚学堂马士兵Java视频教程
  2. 【程序猿历程,史上最全的Java面试题集锦在这里
  3. 【程序猿历程(1),Javaweb视频教程百度云
  4. Notes on MySQL 45 lectures (1-7)
  5. [computer network 12 (1), Shang Xuetang Ma soldier java video tutorial
  6. The most complete collection of Java interview questions in history is here
  7. [process of program ape (1), JavaWeb video tutorial, baidu cloud
  8. Notes on MySQL 45 lectures (1-7)
  9. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  10. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  11. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  12. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  13. 【递归,Java传智播客笔记
  14. [recursion, Java intelligence podcast notes
  15. [adhere to painting for 386 days] the beginning of spring of 24 solar terms
  16. K8S系列第八篇(Service、EndPoints以及高可用kubeadm部署)
  17. K8s Series Part 8 (service, endpoints and high availability kubeadm deployment)
  18. 【重识 HTML (3),350道Java面试真题分享
  19. 【重识 HTML (2),Java并发编程必会的多线程你竟然还不会
  20. 【重识 HTML (1),二本Java小菜鸟4面字节跳动被秒成渣渣
  21. [re recognize HTML (3) and share 350 real Java interview questions
  22. [re recognize HTML (2). Multithreading is a must for Java Concurrent Programming. How dare you not
  23. [re recognize HTML (1), two Java rookies' 4-sided bytes beat and become slag in seconds
  24. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  25. RPC 1: how to develop RPC framework from scratch
  26. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  27. RPC 1: how to develop RPC framework from scratch
  28. 一次性捋清楚吧,对乱糟糟的,Spring事务扩展机制
  29. 一文彻底弄懂如何选择抽象类还是接口,连续四年百度Java岗必问面试题
  30. Redis常用命令
  31. 一双拖鞋引发的血案,狂神说Java系列笔记
  32. 一、mysql基础安装
  33. 一位程序员的独白:尽管我一生坎坷,Java框架面试基础
  34. Clear it all at once. For the messy, spring transaction extension mechanism
  35. A thorough understanding of how to choose abstract classes or interfaces, baidu Java post must ask interview questions for four consecutive years
  36. Redis common commands
  37. A pair of slippers triggered the murder, crazy God said java series notes
  38. 1、 MySQL basic installation
  39. Monologue of a programmer: despite my ups and downs in my life, Java framework is the foundation of interview
  40. 【大厂面试】三面三问Spring循环依赖,请一定要把这篇看完(建议收藏)
  41. 一线互联网企业中,springboot入门项目
  42. 一篇文带你入门SSM框架Spring开发,帮你快速拿Offer
  43. 【面试资料】Java全集、微服务、大数据、数据结构与算法、机器学习知识最全总结,283页pdf
  44. 【leetcode刷题】24.数组中重复的数字——Java版
  45. 【leetcode刷题】23.对称二叉树——Java版
  46. 【leetcode刷题】22.二叉树的中序遍历——Java版
  47. 【leetcode刷题】21.三数之和——Java版
  48. 【leetcode刷题】20.最长回文子串——Java版
  49. 【leetcode刷题】19.回文链表——Java版
  50. 【leetcode刷题】18.反转链表——Java版
  51. 【leetcode刷题】17.相交链表——Java&python版
  52. 【leetcode刷题】16.环形链表——Java版
  53. 【leetcode刷题】15.汉明距离——Java版
  54. 【leetcode刷题】14.找到所有数组中消失的数字——Java版
  55. 【leetcode刷题】13.比特位计数——Java版
  56. oracle控制用户权限命令
  57. 三年Java开发,继阿里,鲁班二期Java架构师
  58. Oracle必须要启动的服务
  59. 万字长文!深入剖析HashMap,Java基础笔试题大全带答案
  60. 一问Kafka就心慌?我却凭着这份,图灵学院vip课程百度云