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
OpenSamlAuthenticationRequestFactory has a method called setProtocolBinding, which allows an application to indicate to IDPs the binding the IDP should use when sending the Response.
Both the SSO Service Location and Binding are in RelyingPartyRegistration.
But the ACS Location is in RelyingPartyRegistration and the ACS Binding is in OpenSamlAuthenticationRequestFactory, which creates some confusion.
For this ticket, OpenSamlAuthenticationRequestFactory#setProtocolBinding should be deprecated and a new method in RelyingPartyRegistration should be introduced that follows the SP metadata naming convention.
The text was updated successfully, but these errors were encountered:
Having the application generate the AuthnRequest fresh allows Spring
Security to back away more gracefully. Using a Consumer implies that
the application will need to undo any values that Spring Security set
that the application doesn't want.
Also, if this does become a configuration burden, it can be simplified
in a separate ticket by exposing the default Converter.
Issue gh-8776
OpenSamlAuthenticationRequestFactory
has a method calledsetProtocolBinding
, which allows an application to indicate to IDPs the binding the IDP should use when sending the Response.Both the SSO Service Location and Binding are in
RelyingPartyRegistration
.But the ACS Location is in
RelyingPartyRegistration
and the ACS Binding is inOpenSamlAuthenticationRequestFactory
, which creates some confusion.For this ticket,
OpenSamlAuthenticationRequestFactory#setProtocolBinding
should be deprecated and a new method inRelyingPartyRegistration
should be introduced that follows the SP metadata naming convention.The text was updated successfully, but these errors were encountered: