<div dir="ltr">Thanks for clarifying Sebi. In this case, let's leave it as is.</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 28, 2016 at 8:26 AM Sebastien Blanc <<a href="mailto:sblanc@redhat.com">sblanc@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Sep 28, 2016 at 11:53 AM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 2016-09-27, Sebastien Blanc wrote:<br>
> I know at least one project (a mbass solution) that is planning to replace<br>
> some "manual" code by using the keycloak-nodejs-auth-utils module. It's in<br>
> an integration layer and it only needs to handle token/grant retrieval and<br>
> refresh.<br>
<br>
</span>In this scenario, they don't have connect or express? If possible,<br>
would you mind to elaborate more?<br></blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>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.<br> <br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span><br>
> But I don't think it would be a real problem if this module is merged<br>
> with connect.<br>
><br>
><br>
><br>
> On Tue, Sep 27, 2016 at 10:59 AM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>><br>
> wrote:<br>
><br>
> > Good morning,<br>
> ><br>
> > Today the only use case scenario for<br>
> > keycloak-nodejs-auth-utils is the usage with keycloak-nodejs-connect for<br>
> > authorization. Besides that I don't see any reason to have it as a<br>
> > separate module. Unless we have plans for new modules like Passport<br>
> > strategies, or embed the authorization bits in some framework<br>
> > non-related with Connect.<br>
> ><br>
> > What do you guys think about merge auth-utils codebase into<br>
> > keycloak-nodejs-connect?<br>
> ><br>
> > --<br>
> ><br>
> > abstractj<br>
> > PGP: 0x84DC9914<br>
> > _______________________________________________<br>
> > keycloak-dev mailing list<br>
> > <a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
> ><br>
<br>
</span>--<br>
<br>
abstractj<br>
PGP: 0x84DC9914<br>
</blockquote></div></div></div></blockquote></div>