You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warning This package is deprecated and will be removed in the future. We will shortly provide more details on removal date, and recommended alternatives.
To improve the statement I suggest provide more details at least link to this thread (for me it took quite some time to find this discussion with handy tips/alternatives from community).
Details
For more details on topic of deprication read this related discussion.
The text was updated successfully, but these errors were encountered:
Bumping this because most connectors have broken examples and getting a working node.js + keycloak solution is turning into a huge headache, with all signs pointing to needing a rewrite soon.
UPDATE: I've found something that works! Keycloak has actually made keycloak-admin-client - it's VERY difficult to find via google because it's buried deep in their monorepo.
Also - the example for it is broken (shocker!). To use it, don't use grantType: 'password', instead use 'client_credentials' and add the client secret in a property named 'clientSecret' on the object you pass to kcAdminClient.
The official Keycloak guides/docs have no mention of this new module and still point to the old one. This took WAY too much time because of Keycloak's outdated documentation, it's such a shame. I hope this saves someone the days that I wasted coming up with a working node solution.
Description
For users it would be handy to add warning with alternatives to docs here. Perhaps link to "nodejs adapter deprication update" post would do the job.
At npm:
To improve the statement I suggest provide more details at least link to this thread (for me it took quite some time to find this discussion with handy tips/alternatives from community).
Details
For more details on topic of deprication read this related discussion.
The text was updated successfully, but these errors were encountered: