Re: [aerogear-dev] [android] Removing AGAuthenticationModule
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?
~ Lukas
On Tue, Sep 16, 2014 at 6:07 PM, Christos Vasilakis <cvasilak(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Attachments:
- attachment.html (text/html — 2.7 KB)