Re: [keycloak-dev] Merge of keycloak-nodejs-connect and keycloak-nodejs-auth-utils
I know at least one project (a mbass solution) that is planning to replace
some "manual" code by using the keycloak-nodejs-auth-utils module. It's in
an integration layer and it only needs to handle token/grant retrieval and
refresh.
But I don't think it would be a real problem if this module is merged
with connect.
On Tue, Sep 27, 2016 at 10:59 AM, Bruno Oliveira <bruno(a)abstractj.org>
wrote:
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
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
Attachments:
- attachment.html (text/html — 1.6 KB)