...
Spring Framework 6.0.5 and 6.0.6 are out, but not integrated. We expect their new signing key to be published on their web site soon, now.
John
Marvin
Phil
Rod
Scott
Started null cleanup on OpenSAML
Reviewing HttpClient changes
Working on SP configuration “framework” based around Application interface
Instead of reusing RelyingParty resolver, Application will do its own resolution of default or overridden RP config
Moved “default” SecurityConfiguration into RelyingPartyConfiguration
More sensible than the old approach of the resolver exposing it
Obviates the need for profile-specific security configs in most cases but still an option
Deployer declares Application beans that can reference shared or contain specific RelyingParty/Profile configurations
All the beans typically inside RelyingPartyResolver service will be in the “ServiceProviderService” (no idea what to call it yet) that exposes the Applications and other Remoted endpoints that do work
With Spring magic, no need for the current idea of a “default” Application and nested overrides. Just map requests to an Application, and share beans as needed to have defaults and special settings