Authentication options for API serving website and mobile app -


as part of wider learning process, looking build website , mobile application common api data storage , retrieval (think of simple cms). mobile app have additional functionality things offline storage (of draft articles example if offline) , accessing media/camera etc. there public facing home page secure area each member create/modify own content.

i have done lot of reading around feedback on recommended architecture in terms of how handle authentication (i comfortable building app , website , api itself). let's @ point in future might open api third parties. there whole host of options out there can't seem find decent diagrams representing flows. pros , cons scenario , links diagrams of below options great.

would rather not require users login every time access app (or website come that) , worried having private keys on mobile app also.

this must common scenario nowadays , wondering experience people have each of these.

oauth 1a oauth 2 hmac basic ssl apache shiro hosted services such stormpath other options

it nice end users able login social accounts (twitter, facebook et al) being able create account website/app also.


Comments

Popular posts from this blog

Delphi XE2 Indy10 udp client-server interchange using SendBuffer-ReceiveBuffer -

Qt ActiveX WMI QAxBase::dynamicCallHelper: ItemIndex(int): No such property in -

Enable autocomplete or intellisense in Atom editor for PHP -