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
Saml2WebSsoAuthenticationFilter has constant DEFAULT_FILTER_PROCESSES_URI. The logic of the filter heavily relies on it. This configuration makes possibility of providing "assertionConsumerServiceUrlTemplate" in RelyingPartyRegistration useless. If application needs to use different format than DEFAULT_FILTER_PROCESSES_URI, the response from identity provider is not processed.
Actual Behavior
Saml2WebSsoAuthenticationFilter is not called or RelyingPartyRegistration is not detected when executing filter logic
Expected Behavior
Saml2WebSsoAuthenticationFilter should be configurable.
Version
5.2.0.RELEASE
The text was updated successfully, but these errors were encountered:
Note, this is not read from the RelyingPartyRegistration.getAssertionConsumerServiceUrlTemplate field. This field is used when generating metadata or authentication request forms.
The RelyingPartyRegistration gets resolved after the filter has been invoked and is processing the request
Summary
Saml2WebSsoAuthenticationFilter has constant DEFAULT_FILTER_PROCESSES_URI. The logic of the filter heavily relies on it. This configuration makes possibility of providing "assertionConsumerServiceUrlTemplate" in RelyingPartyRegistration useless. If application needs to use different format than DEFAULT_FILTER_PROCESSES_URI, the response from identity provider is not processed.
Actual Behavior
Saml2WebSsoAuthenticationFilter is not called or RelyingPartyRegistration is not detected when executing filter logic
Expected Behavior
Saml2WebSsoAuthenticationFilter should be configurable.
Version
5.2.0.RELEASE
The text was updated successfully, but these errors were encountered: