-
Notifications
You must be signed in to change notification settings - Fork 421
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
Archive the Node.js Connect adapter on Github #456
Comments
Hi. When is "the final deprecation date"? A link in the README to explain why you are archiving / deprecating / removing this package would be really helpful too! |
Like already mentioned no dates have been set. |
Do you mean date to provide more details? Is code vulnerable, unmaintainable? Is there an alternative we should know about? Message on README.md is very terse and cryptic. |
We have not yet set a date for full deprecation and removal. We will continue to land CVE fixes, but will no longer be accepting new features. |
Hi! We're looking to integrate Keycloak authentication into our NestJS-App. Seeing that this module sadly got deprecated, are there any alternatives that you could recommend? Thanks a lot. |
@mircicd I think the best place to look for that is in the discussion around this topic. |
Once we have passed the final deprecation date of the Node.js Connect adapter we will have archive the corresponding GitHub repository and update the README to show the final deprecation notice.
Please check: keycloak/keycloak#9818
The text was updated successfully, but these errors were encountered: