Jean-Pierre Bergamin (Migrated from SEC-1842) said:
Namespace configuration should allow the usage of a custom AuthenticationManager. In our case, this AuthenticationManager would be an imported OSGi service.
If the namespace config really must rely on having a ProviderManager (and not only an AuthenticationManager as expected), an Interface for ProviderManager should be introduced so that it can be e.g. published as an OSGi service via this interface.
Luke Taylor said:
You can now set custom AuthenticationManager references in the namespace, using the authentication-manager-ref attribute introduced in SEC-1847.
Is is actually still possible to override the default global AuthenticationManager by registering a bean with the same name (rather than using the authentication-manager namespace element).
Marking as "Won't fix" since this is superseded by SEC-1847.
Jean-Pierre Bergamin said:
That sounds like what we really needed. Thanks for introducing this so quickly.