Repository navigation
Replies: 3 comments 2 replies
|
As long as there is an adequate replacement method (and I think it is) the removal should be no problem. |
0 replies
|
@hmlnarik what you suggest make sense. I'd suggest a blog post with all the details about which APIs will become EOL by Sept 15, so it's transparent to our community. Here's an example from Node.js https://nodejs.org/api/deprecations.html |
2 replies
|
+1 for remove these deprecated methods. The 2 years period should be enough and there was already multiple Keycloak releases with the deprecated methods. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
Since 2020, multiple methods became deprecated, usually replaced by a similar method with a consistent parameter positions and / or stream variants. Examples of these transitions are below.
I propose removing all of these deprecated methods in Keycloak 20. Maintaining the deprecated methods brings no value, and the deprecation period has been IMO sufficient.
Please state your agreement or concerns with this intention by Sep 15 here.
Cc: @keycloak/kc-maintainers @keycloak/kc-external-maintainers
Scope
All
*Modelclasses and all data-oriented*Providerclasses likeUserProvider,GroupProvideretc.Examples of these methods
Remove
getRequiredCredentials()here:keycloak/server-spi/src/main/java/org/keycloak/models/RealmModel.java
Lines 270 to 282 in 4323d79
Remove
searchForGroupByName()here:keycloak/server-spi/src/main/java/org/keycloak/storage/group/GroupLookupProvider.java
Lines 37 to 65 in 4323d79
All reactions