Good morning,
Today the only use case scenario for
keycloak-nodejs-auth-utils is the usage with keycloak-nodejs-connect for
authorization. Besides that I don't see any reason to have it as a
separate module. Unless we have plans for new modules like Passport
strategies, or embed the authorization bits in some framework
non-related with Connect.
What do you guys think about merge auth-utils codebase into
keycloak-nodejs-connect?
--
abstractj
PGP: 0x84DC9914
Show replies by date