[keycloak-dev] Merge of keycloak-nodejs-connect and keycloak-nodejs-auth-utils
lholmqui at redhat.com
Tue Sep 27 14:43:07 EDT 2016
that probably makes sense to merge, as long as the utils api is still
available after the merge
On Tue, Sep 27, 2016 at 2:40 PM, Sebastien Blanc <sblanc at redhat.com> wrote:
> 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 at abstractj.org>
>> 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
>> PGP: 0x84DC9914
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the keycloak-dev