<div dir="ltr"><div>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. <br>But I don't think it would be a real problem if this module is merged with connect. <br></div><br><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 10:59 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">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>
______________________________<wbr>_________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">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/<wbr>mailman/listinfo/keycloak-dev</a><br>
</blockquote></div><br></div>