Hi,
perhaps this is more "AeroGear-Security VS HTTP Basic/Digest", but first some background informations:
our different "AuthenticationModule" implementations, for Android, iOS and JavaScript, were created for the AeroGear-Security REST-APIs, which are described here:
Here are the three different client platform implementations:
* Android:
* iOS:
* JavaScript:
So, basically the interface(or the different implementations) covers the following functionality, described in the above spec:
* enroll
* login
* logout
So far so good.
Instead, the "login", is _only_ applying the credentials to that subsequent requests can read (a) protected URL(s). Similar to "logout": Only a _reset_ of the credentials is happening. No server endpoint is invoked.
Similar to the "enroll"; The iOS proposal throws an exception, similar to the Android version:
To me, looks like none of the methods of the "AuthenticationModule interface" are properly used, or am I wrong?
I think my question is: Does it really make sense to kinda try to add the BASIC/DIGEST support into the "AuthenticationModule interface"?? or, could there be something else ?
Not sure, I guess since I am not sure, I am asking here :)
Any feedback is appreciated!
Thanks!
Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf