Then we may want to remove it in 2.0 until we have a use case for it. WDYT Luke?

On Fri, Sep 19, 2014 at 3:28 PM, Lucas Holmquist <lholmqui@redhat.com> wrote:

On Sep 19, 2014, at 9:22 AM, Summers Pittman <supittma@redhat.com> wrote:

On Friday, September 19, 2014 7:12:01 AM, Lukáš Fryč wrote:
Right now Auth module does not seem to serve any purpose anymore,

but as we have discussed on JS meeting,

there may possibility to integrate with third-party endpoints such as
Keycloak, Auth0, Mozilla Personas, etc.


As I can foresee it, Auth module may serve a purpose of single point
holding authentication data such as tokens,
that can be used  for setting up authentication of either third-party
frameworks we use (e.g. in demos, such as in AngularJS this can be
used to register itself to HTTP request interceptor),

or it may handle authentication for our modules, e.g. Data Sync.

I'm not saying we shouldn't remove it at this point, but my question
is rather what do we recommend instead?
I'm not saying we remove the auth module system.  I'm just proposing we 
remove that one implementation because it doesn't do anything.

right,  we, JS, only have 1 adapter, REST,  so it might be that we just remove it totally





~ Lukas

On Tue, Sep 16, 2014 at 6:07 PM, Christos Vasilakis
<cvasilak@gmail.com <mailto:cvasilak@gmail.com>> wrote:

   +1 don’t think it makes sense to keep it,  for iOS it was used
   only for the Controller case since basic/digest was already
   handled by the platform

   -
   Christos

   On Sep 16, 2014, at 6:44 PM, Summers Pittman <supittma@redhat.com
   <mailto:supittma@redhat.com>> wrote:

AGAuthenticationModule was originally made to
   login/logout/register with
the AeroGear controller.  Since controller is dead in a ditch
   somewhere,
for AGDroid 2.0 I'm proposing we remove it from the platform.
   This will
leave HttpBasicAuthenticationModule and
   HttpDigestAuthenticationModule.
However I know this also exists for iOS and Javascript so I'm
   putting
this post up for discussion.

wdyt?
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev


   _______________________________________________
   aerogear-dev mailing list
   aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
   https://lists.jboss.org/mailman/listinfo/aerogear-dev




_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev