Repository navigation
v26.6.30
Spring Security parity — Tier 1: the authentication spine. The core of
Spring Security's authentication architecture, the foundation later tiers build
on. All additive (no behaviour change to existing code).
Added
- Authentication manager spine —
AuthenticationManager/ProviderManager
/AuthenticationProvider(Spring's authentication architecture). An
AuthenticationRequest(UsernamePassword/BearerToken,#[non_exhaustive])
is resolved by the first supporting provider;BearerTokenAuthenticationProvider
adapts the existingVerifierinto the spine. UserDetails+ DAO authentication —UserDetails(with the four Spring
account-status flags),UserDetailsService,UserDetailsChecker/
AccountStatusUserDetailsChecker,InMemoryUserDetailsService, and
DaoAuthenticationProvider(an enumeration-safe username/password provider:
unknown user and wrong password both fail asBad credentialswith comparable
bcrypt work).DelegatingPasswordEncoder— Spring's recommended{id}-prefixed password
storage ({bcrypt}/{argon2}/{noop}),upgrade_encodingfor re-hash-on-login,
and seamless migration of legacy bare hashes; plusNoOpPasswordEncoder.SecurityContextRepository— the pluggable between-request context store
(HttpSessionSecurityContextRepositorydefault,NullSecurityContextRepository
for stateless surfaces).SessionAuthenticationLayernow loads the context
through a swappable repository instead of a hardcoded session key; added
Authentication::is_authenticated().AuthenticationEventPublisher—AuthenticationEvent::{Success,Failure}
published byProviderManagerfor every outcome (LoggingAuthenticationEvent- Publisherdefault).- Pluggable
AuthenticationEntryPoint/AccessDeniedHandler(Spring's
ExceptionTranslationFilterseam) —FilterChainrenders its401/403
through them, defaulting to the canonical problem+json and overridable via
with_authentication_entry_point/with_access_denied_handler.
Known limitations (roadmap)
ProviderManagercontinues to the next supporting provider after a failure
(Spring rethrows anAccountStatusExceptionimmediately). With one provider
per credential kind — the norm — the outcome is identical; a terminal/continue
error taxonomy is a follow-up.DelegatingPasswordEncoder::upgrade_encodingcompares the stored{id}only
(algorithm migration); it does not yet flag a within-algorithm work-factor
increase for re-hash.with_defaults()registers{noop}(plaintext — dev only, as Spring does)
and verifies legacy unprefixed hashes as bcrypt to ease migration; disable
the latter withwith_unprefixed(None)for Spring's stricter reject-on-bare
behaviour.