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
The gateway sends its authentication requests to Engineblock via http GET, but includes the signature in the XML message. This is not a valid combination according to the protocol; it should be encoded in the get parameter Signature and the corresponding GET parameter SigAlg.
It does currently work with EB. However, in order to keep the complexity within the platform under control, all components should use the same, and valid bindings.
This is not trivial. Currently OIDC-NG uses the spring-security-saml-core library which is currently being incorporated into spring-security. There is a related issue: spring-projects/spring-security#7711
This issue is imported from pivotal - Originaly created at Aug 21, 2020 by Thijs Kinkhorst
The gateway sends its authentication requests to Engineblock via http GET, but includes the signature in the XML message. This is not a valid combination according to the protocol; it should be encoded in the get parameter Signature and the corresponding GET parameter SigAlg.
It does currently work with EB. However, in order to keep the complexity within the platform under control, all components should use the same, and valid bindings.
UPDATE from spring:
Support for customizing the AuthnRequest was added in 5.4.: https://docs.spring.io/spring-security/site/docs/5.4.0/reference/html5/#servlet-saml2login-sp-initiated-factory-custom-authnrequest . You can use OpanSamlAuthenticationRequestFactory#setAuthenticationRequestContextConverter to supply a converter creates the AuthnRequest you need, though it may be easier to register a custom AuthnRequestMarshaller with OpenSAML.
The text was updated successfully, but these errors were encountered: