Remove Deprecated OpenSAML 3 Support
Closes gh-10556
This commit is contained in:
@@ -154,14 +154,6 @@ Instead, such classes as `OpenSamlAuthenticationRequestFactory` and `OpenSamlAut
|
||||
|
||||
For example, once your application receives a `SAMLResponse` and delegates to `Saml2WebSsoAuthenticationFilter`, the filter delegates to `OpenSamlAuthenticationProvider`:
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
For backward compatibility, Spring Security will use the latest OpenSAML 3 by default.
|
||||
Note, though that OpenSAML 3 has reached it's end-of-life and updating to OpenSAML 4.x is recommended.
|
||||
For that reason, Spring Security supports both OpenSAML 3.x and 4.x.
|
||||
If you manage your OpenSAML dependency to 4.x, then Spring Security will select its OpenSAML 4.x implementations.
|
||||
====
|
||||
|
||||
.Authenticating an OpenSAML `Response`
|
||||
image:{figures}/opensamlauthenticationprovider.png[]
|
||||
|
||||
|
||||
@@ -6,6 +6,8 @@ Below are the highlights of the release.
|
||||
|
||||
== Breaking Changes
|
||||
|
||||
* https://github.com/spring-projects/spring-security/issues/10556[gh-10556] - Remove EOL OpenSaml 3 Support.
|
||||
Use the OpenSaml 4 Support instead.
|
||||
* https://github.com/spring-projects/spring-security/issues/8980[gh-8980] - Remove unsafe/deprecated `Encryptors.querableText(CharSequence,CharSequence)`.
|
||||
Instead use data storage to encrypt values.
|
||||
* https://github.com/spring-projects/spring-security/issues/11520[gh-11520] - Remember Me uses SHA256 by default
|
||||
|
||||
Reference in New Issue
Block a user