In this case, couldn't the device just use the registration API?
On 1/24/2014 12:54 PM, Matthias Wessendorf wrote:
+1 on this scenario
There is a different scenario:
* the mobile app does not require an actual user (e.g. think about
something like a News-App (e.g. "ESPN Sports Ticker")), but the device
still needs to be registered w/ a server, so that the server later can
use the device metadata for sending push notifications to the iOS /
Android device. The AeroGear UnifiedPush Server is doing it (currently)
via HTTP Basic (see [1]).
IMO, its not a pure enterprise use case. I access my brokerage acct via my ipad and browser via the same credentials.
Is this some scenario you are interested in supporting as well? Or is
the (current) focus more around storing 'devices' / 'device metadata'
under a real user (which is most-likely a pure enterprise use-case)?