Geek Answers Handbook

OAuth 2.0 Client Definition

I am developing a REST-based API for our system. We will have several clients:

  • Web browsers - they will access our API after loading the HTML5 application
  • Mobile applications developed by us.
  • Third party mobile apps

I wanted to ask what strategy should we use when identifying customers. For instance.

  • each user in our system should be defined as a client, because it must be authenticated or is it a web client, which is considered one client?

  • do we assign a client to our iPhone application, and the other to our android application?

  • Does every third-party developer using our API have a separate client identifier?

Thank,

Assaf

+5
source share
2

Google API, . API Access, . , , -, Android iPhone. .

:

enter image description here

+2

. . , :

a) OAuth. OAuth - . b) OAuth,

, . OAuth 2 (http://tools.ietf.org/html/draft-ietf-oauth-v2-25), - " ", , , , , 1 OAuth

c) , , , - , .

, , OAuth , , ,

0

More articles:


All Articles