Description
The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in https://github.com/apache/fineract/pull/863 as part of FINERACT-963 introduced usage of @Deprecated code, which we are trying to avoid (and which since FINERACT-959 we're intentionally making the build fail).
I'm going to use a @SuppressWarnings("deprecation") to be able to do the upgrade anyway, because upgrading a security related library to its latest version seems like a sensible thing to do, but we really should remove the suppression and switch to using Spring's newer APIs.
https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
affects UserDetailsApiResource and TwoFactorAuthenticationFilter.createUpdatedAuthentication()
Attachments
Issue Links
- Blocked
-
FINERACT-1305 Release Apache Fineract v1.5.0
- Resolved
- fixes
-
FINERACT-1033 Fineract OAuth Token Change Bug
- Open
-
FINERACT-1282 Health actuator gives 404 when in oauth mode
- Resolved
-
FINERACT-1352 OAuth Bad credentials error
- Resolved
-
FINERACT-1261 support for external Oauth provider
- Resolved
-
FINERACT-1143 Add Test Coverage for OAuth Support
- Resolved
- is fixed by
-
FINERACT-1057 Running -Psecurity=oauth leads to memory leak issue
- Closed
- is required by
-
FINERACT-963 Upgrade about 15 of our 3rd-party libraries to their latest versions
- Resolved
- relates to
-
FINERACT-1261 support for external Oauth provider
- Resolved
- requires
-
FINERACT-1145 OAuth Support documentation is missing
- Resolved
-
FINERACT-1144 OAuth broken (or is it?)
- Closed
-
FINERACT-1143 Add Test Coverage for OAuth Support
- Resolved
- links to