Because now things (pipes) which use the AuthModule do not have to be aware of the
implementation details of the Auth module.
----- Original Message -----
From: "Matthias Wessendorf" <matzew(a)apache.org>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Friday, November 9, 2012 9:18:27 AM
Subject: Re: [aerogear-dev]
[Android] AuthenticationModule.applyAuthentication(HttpProvider)
On Fri, Nov 9, 2012 at 3:03 PM, Summers Pittman <supittma(a)redhat.com> wrote:
And as such those methods are on the AuthModule interface.
==> those are login, enroll, logout - right ? Yes, same location as
well on my side...
TokenHeader is a RestAuthModule specific thing and only on its
specific ConfigObject and impl
that's fine.....
but why adding this
"AuthenticationModule.applyAuthentication(HttpProvider)" to the actual
public auth module?
----- Original Message -----
From: "Matthias Wessendorf" <matzew(a)apache.org>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Friday, November 9, 2012 9:00:23 AM
Subject: Re: [aerogear-dev] [Android]
AuthenticationModule.applyAuthentication(HttpProvider)
Well, we never really discussed much about those extension options
(e.g. SPIs) or what not.
But, still "enroll", "login", or "logout" are way higher
lever
compared to something technically like "apply auth headers"
(something like that could be in the SPI)
-M
On Fri, Nov 9, 2012 at 2:45 PM, Summers Pittman <supittma(a)redhat.com> wrote:
> What happens if the implementation of your Auth module doesn't have a field (or
objective c equavalent) of Auth token?
>
> ----- Original Message -----
> From: "Matthias Wessendorf" <matzew(a)apache.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
> Sent: Friday, November 9, 2012 8:28:19 AM
> Subject: Re: [aerogear-dev] [Android]
AuthenticationModule.applyAuthentication(HttpProvider)
>
> in the iOS the "rest pipe impl" reads the token from the given "auth
> module impl" (an internal API cast) and just applies it in to the
> headers on the AFNetworking stuff.
>
> -Matthias
>
>
> On Fri, Nov 9, 2012 at 2:22 PM, Summers Pittman <supittma(a)redhat.com> wrote:
>> So, in your mind, where should the handle for applying session security go?
(Header Tokens, signing, url params, etc)
>>
>> ----- Original Message -----
>> From: "Matthias Wessendorf" <matzew(a)apache.org>
>> To: "AeroGear Developer Mailing List"
<aerogear-dev(a)lists.jboss.org>
>> Sent: Friday, November 9, 2012 1:47:50 AM
>> Subject: Re: [aerogear-dev] [Android]
AuthenticationModule.applyAuthentication(HttpProvider)
>>
>> I have seen that method.
>>
>> For me, I am not sure I really want to expose something like that to
>> the endusers... For me the auth module is basically the facility where
>> users of the library (-> app devs) are doing enrollment, login and
>> logout
>>
>> Not really to thrilled about doing that in iOS...
>>
>> -M
>>
>> On Fri, Nov 9, 2012 at 4:55 AM, Summers Pittman <supittma(a)redhat.com>
wrote:
>>> I added a method to AuthenticationModule,
"applyAuthentication(HttpProvider)". Before the RestAdapter (subclass of Pipe)
class had to know details about how the AuthModule / Auth Strategy worked to apply a
token. IN this case the handling of security connections is done by the module instead of
the Pipe.
>>>
>>> Wdyt about adding it to the ios and js libraries?
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog:
http://matthiaswessendorf.wordpress.com/
>> sessions:
http://www.slideshare.net/mwessendorf
>> twitter:
http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> 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
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
>
> _______________________________________________
> 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
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
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
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev