[v4.4.1] - Complete Validator

Full Changelog: v4.4.0...v4.4.1

[v4.3.0] - Validator

• The Spring Authorization Server recommends using functional interfaces for validation (https://docs.spring.io/spring-authorization-server/reference/protocol-endpoints.html).
• Instead of applying OAuth2ClientCredentialsAuthenticationContext, additional parameters from OAuth2ClientAuthenticationToken were used. I could create OAuth2ClientCredentialsAuthenticationContext in OpaqueGrantTypeAuthenticationProvider, but I believe that would be a bit overkill.
• Renamed RegisteredClientRepositoryImpl to CacheableRegisteredClientRepositoryImpl to reflect its original caching functionality.
• Renamed Integration Test Controller names

[v4.2.0] - Optional Authorization Consent Module

• From this point forward, the "OAuth2 - Authorization Code" has been officially released and is no longer in beta.
• Future releases will focus on improving test coverage and refactoring, with no new features planned for the time being.

Full Changelog: v4.2.0...v4.2.0

[v4.1.0] - Normalize grant_type names and add OpaqueGrantTypeAuthenticationProvider to align with Spring Authorization Server standards

Full Changelog: v4.0.1...v4.1.0

[v4.0.1] - Spring Oauth2 EasyPlus

Full Changelog: v4.0.0...v4.0.1

[v4.0.0] - Spring Oauth2 EasyPlus

Full Changelog: v3.5.0...v4.0.0

[v3.5.0] - Fully extensible KnifeUserInfo

Full Changelog: v3.4.0...v3.5.0

[v3.4.0] - Introduce API-based Introspection

• Introspection type configuration:
  • api: The Resource Server sends introspection requests to the Authorization Server (better scalability, Some test codes are currently NOT working due to the following introspection URI calls)
  • database (default): The Resource Server and Authorization Server share the same database (faster performance)

[v3.3.0] - Improve KnifeErrorMessages && UserNameNotFoundException Message Management

1. Renamed ErrorMessages to KnifeErrorMessages, now capable of holding the UserDetails object.
2. The displayed message (userMessage) of UserNameNotFoundException is exclusively managed by the UserDetailsService implementation.

[v3.2.0] - Introduce Authorization Code Flow module

Full Changelog: v3.1.2...v3.2.0