Allow customization of redirect strategy
The default redirect strategy will provide authorization redirect URI within HTTP 302 response Location header. Allowing the configuration of custom redirect strategy will provide an option for the clients to obtain the authorization URI from e.g. HTTP response body as JSON payload, without a need to handle automatic redirection initiated by the HTTP Location header. Closes gh-11373
This commit is contained in:
@@ -984,6 +984,11 @@ Reference to the `AuthorizationRequestRepository`.
|
||||
Reference to the `OAuth2AuthorizationRequestResolver`.
|
||||
|
||||
|
||||
[[nsa-oauth2-login-authorization-redirect-strategy-ref]]
|
||||
* **authorization-redirect-strategy-ref**
|
||||
Reference to the authorization `RedirectStrategy`.
|
||||
|
||||
|
||||
[[nsa-oauth2-login-access-token-response-client-ref]]
|
||||
* **access-token-response-client-ref**
|
||||
Reference to the `OAuth2AccessTokenResponseClient`.
|
||||
@@ -1084,6 +1089,11 @@ Configures xref:servlet/oauth2/client/authorization-grants.adoc#oauth2Client-aut
|
||||
Reference to the `AuthorizationRequestRepository`.
|
||||
|
||||
|
||||
[[nsa-authorization-code-grant-authorization-redirect-strategy-ref]]
|
||||
* **authorization-redirect-strategy-ref**
|
||||
Reference to the authorization `RedirectStrategy`.
|
||||
|
||||
|
||||
[[nsa-authorization-code-grant-authorization-request-resolver-ref]]
|
||||
* **authorization-request-resolver-ref**
|
||||
Reference to the `OAuth2AuthorizationRequestResolver`.
|
||||
|
||||
Reference in New Issue
Block a user