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
OpenSamlImplementation is a package-private Spring Security class that exists to remove some of the boilerplate needed to configure and work with OpenSAML.
In effect, it does four things:
Bootstraps OpenSAML with reasonable defaults
Builds OpenSAML XMLObjects
Marshals OpenSAML XMLObjects
Unmarshals OpenSAML XMLObjects
While it was convenient to have in the early stages of creating saml2-service-provider, there's value in breaking it up into its individual components.
The above plan requires minimal code duplication as the authentication provider is largely unmarshalling objects while the authentication request factory is marshalling them. Additionally, the marshalling support in OpenSamlImplementation is largely specific to AuthnRequest.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
OpenSamlImplementation
is a package-private Spring Security class that exists to remove some of the boilerplate needed to configure and work with OpenSAML.In effect, it does four things:
XMLObject
sXMLObject
sXMLObject
sWhile it was convenient to have in the early stages of creating
saml2-service-provider
, there's value in breaking it up into its individual components.OpenSamlAuthenticationProvider
should use OpenSAML directly - OpenSamlAuthenticationProvider should use OpenSAML directly #8773OpenSamlAuthenticationRequestFactory
should use OpenSAML directly - OpenSamlAuthenticationRequestFactory should use OpenSAML directly #8774The above plan requires minimal code duplication as the authentication provider is largely unmarshalling objects while the authentication request factory is marshalling them. Additionally, the marshalling support in
OpenSamlImplementation
is largely specific toAuthnRequest
.The text was updated successfully, but these errors were encountered: