Cookie-based authentication and web API -
i'm architecting public web api service. equally consumed web pages , native mobile apps (ios, android , windows 8).
should use cookie-based authentication? mean, best practice scenario?
futher info:
after little research in authentication/authorization/openid-connect field realized of handled browser, mean, redirects, coockie insertion , related "boiler-plate" stuff... when think boiler-plate have duplicate in natives apps, wonder if model best mobile apps. mean, maybe theres more mobile-native-friendly way...
ps: know little generic still, it's i'm begginer in field of security , dont know how express doubts/concerns/"laziness" still...
the api should stateless, , not manage sessions. each request api should made authentication details (e.g. oauth token).
if web pages , mobile applications need maintain kind of session, should them clients of service maintain state. instance, web page might set session cookie user, native mobile app might want different approach.
see also: if rest applications supposed stateless, how manage sessions?
Comments
Post a Comment