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&gt; 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 > _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

On 2016-09-27, Sebastien Blanc 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. In this scenario, they don't have connect or express? If possible, would you mind to elaborate more?

> 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&gt; > 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 > > -- abstractj PGP: 0x84DC9914

Thanks for clarifying Sebi. In this case, let's leave it as is. On Wed, Sep 28, 2016 at 8:26 AM Sebastien Blanc <sblanc(a)redhat.com&gt; wrote: > On Wed, Sep 28, 2016 at 11:53 AM, Bruno Oliveira <bruno(a)abstractj.org&gt; > wrote: > >> On 2016-09-27, Sebastien Blanc 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. >> >> In this scenario, they don't have connect or express? If possible, >> would you mind to elaborate more? >> > > Sure. In this use case the nodejs app act as a "client" for a third > application (the UnifiedPush Server) that is protected by KC. The > authentification system of the whole system is not based on KC (not yet ;) > ) and for now the nodejs needs to retrieve "manually" a token to be able to > pass it to the requests to the UPS. > > >> >> > 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&gt; >> > 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 >> > > >> >> -- >> >> abstractj >> PGP: 0x84DC9914 >> > _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev