-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecation of Keycloak OpenID Connect Node.js Adapter #110
Comments
I think the proper move would be to implement calling Keycloak's authorization API ourselves instead of relying on their official Node.js adapter. I assume authorization services won't be going away soon. The implementation is all there and all we need to do is move over the implementation into typescript and use an http client (i.e axios or node net) |
Maybe this code should go in another standalone repo without nest dependencies ? This could also implement a passport strategy, as passport is the recommanded way to bring authentication in NestJS (according to official docs). |
According to the official deprecation announcement, openid-client seams to be the recommended library for nodejs. Maybe it makes sense to use this as the underlying library. |
We could probably migrate most parts to openid-client but it could not be said the same for Keycloak's authorization services. |
I just released a very first version of an OpenID Connect passport strategy here. It is tested against keycloak and can replace the JWT Token verification of official (and deprecated) keycloak node.js adapter. I plan to add more packages in this repository with a single objective in mind for now : have the same features as |
Hello, Are there any upgrade expectations to address the deprecated library? |
First, thanks for your work on this library!
According to the official Deprecation of Keycloak adapters post (and the corresponding GitHub discussion), the keycloak-nodejs-connect adapter (which this library relies on) is now being deprecated and will receive major/minor releases only until September 2022.
Even though they are still looking around for the best alternative for users, they suggest the openid-client package in the mentioned blog post.
I'm kindly asking whether you plan on migrating this library to an alternative, such as the
openid-client
package.The text was updated successfully, but these errors were encountered: