Repository navigation
Post adapter deprecation notices in more places #14233
Replies: 4 comments 1 reply
|
Absolutely agree. In my opinion the adapters shouldn't even be uploaded to Maven starting with 19.X. Otherwise a lot of developers might not even realize that the adapters are no longer supported. |
|
I opened a ticket for this issue: #17341 |
|
Note the latest live documentation still contains: Keycloak can be secured by supplied adapters that are usually easier to use and provide better integration with Keycloak. (aside from the status of the supplied adapters, the statement is nonsense -- the goal is to secure the application, not to secure Keycloak) https://www.keycloak.org/docs/latest/securing_apps/ The "Other OpenID Connect Libraries" should be moved from 2.5 to 2.2, and the existing 2.1-2.3 should be removed or pushed back and prominently labelled as legacy |
|
Can we do something more on this front please (mention the exact adapters that are deprecated)? At the very least, mark the specific adapter Java classes as deprecated in code. |
|
Totally agree that we need to advertise this more widely, and we will work on that. Based on feedback we have revised our plans, please take a look at https://www.keycloak.org/2023/03/adapter-deprecation-update.html. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am not sure how it is for the other adapters, but for the node-js adapter there are only 2 places that mention the deprecation that are very easy to miss:
I think that mentioning the deprecation is warranted in at least the following locations:
All reactions