You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
=== Use `RelyingPartyRegistration` updated methods
2019
+
2020
+
In an early release of Spring Security's SAML support, there was some ambiguity on the meaning of certain `RelyingPartyRegistration` methods and their function.
2021
+
As more capabilities were added to `RelyingPartyRegistration`, it became necessary to clarify this ambiguity by changing method names to ones that aligned with spec language.
2022
+
2023
+
The deprecated methods in `RelyingPartyRegstration` are removed.
2024
+
To prepare for that, consider the following representative usage of `RelyingPartyRegistration`:
val assertingPartyEntityId: String = registration.getAssertingPartyDetails().getEntityId()
2068
+
val assertionConsumerServiceLocation: String = registration.getAssertionConsumerServiceLocation()
2069
+
val singleSignOnServiceLocation: String = registration.getAssertingPartyDetails().getSingleSignOnServiceLocation()
2070
+
val entityId: String = registration.getEntityId()
2071
+
val verifying: List<Saml2X509Credential> = registration.getAssertingPartyDetails().getVerificationX509Credentials()
2072
+
----
2073
+
====
2074
+
2075
+
For a complete listing of all changed methods, please see {security-api-url}org/springframework/security/saml2/provider/service/registration/RelyingPartyRegistration.html[``RelyingPartyRegistration``'s JavaDoc].
2076
+
2018
2077
== Reactive
2019
2078
2020
2079
=== Use `AuthorizationManager` for Method Security
0 commit comments