<div dir="ltr">Then we may want to remove it in 2.0 until we have a use case for it. WDYT Luke?</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 19, 2014 at 3:28 PM, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><div>On Sep 19, 2014, at 9:22 AM, Summers Pittman <<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>> wrote:</div><br><blockquote type="cite"><div style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">On Friday, September 19, 2014 7:12:01 AM, Lukáš Fryč wrote:<br><blockquote type="cite">Right now Auth module does not seem to serve any purpose anymore,<br><br>but as we have discussed on JS meeting,<br><br>there may possibility to integrate with third-party endpoints such as<br>Keycloak, Auth0, Mozilla Personas, etc.<br><br><br>As I can foresee it, Auth module may serve a purpose of single point<br>holding authentication data such as tokens,<br>that can be used for setting up authentication of either third-party<br>frameworks we use (e.g. in demos, such as in AngularJS this can be<br>used to register itself to HTTP request interceptor),<br><br>or it may handle authentication for our modules, e.g. Data Sync.<br><br>I'm not saying we shouldn't remove it at this point, but my question<br>is rather what do we recommend instead?<br></blockquote>I'm not saying we remove the auth module system. I'm just proposing we<span> </span><br>remove that one implementation because it doesn't do anything.<br></div></blockquote><div><br></div></span><div>right, we, JS, only have 1 adapter, REST, so it might be that we just remove it totally</div><div><div class="h5"><br><blockquote type="cite"><div style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><br><br><blockquote type="cite"><br>~ Lukas<br><br>On Tue, Sep 16, 2014 at 6:07 PM, Christos Vasilakis<br><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a><span> </span><<a href="mailto:cvasilak@gmail.com" target="_blank">mailto:cvasilak@gmail.com</a>>> wrote:<br><br> +1 don’t think it makes sense to keep it, for iOS it was used<br> only for the Controller case since basic/digest was already<br> handled by the platform<br><br> -<br> Christos<br><br> On Sep 16, 2014, at 6:44 PM, Summers Pittman <<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a><br> <<a href="mailto:supittma@redhat.com" target="_blank">mailto:supittma@redhat.com</a>>> wrote:<br><br><blockquote type="cite">AGAuthenticationModule was originally made to<br></blockquote> login/logout/register with<br><blockquote type="cite">the AeroGear controller. Since controller is dead in a ditch<br></blockquote> somewhere,<br><blockquote type="cite">for AGDroid 2.0 I'm proposing we remove it from the platform.<br></blockquote> This will<br><blockquote type="cite">leave HttpBasicAuthenticationModule and<br></blockquote> HttpDigestAuthenticationModule.<br><blockquote type="cite">However I know this also exists for iOS and Javascript so I'm<br></blockquote> putting<br><blockquote type="cite">this post up for discussion.<br><br>wdyt?<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><span> </span><<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">mailto:aerogear-dev@lists.jboss.org</a>><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><br><br> _______________________________________________<br> aerogear-dev mailing list<br> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><span> </span><<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">mailto:aerogear-dev@lists.jboss.org</a>><br> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br><br><br><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></blockquote></div></div></div><br></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>