OAuth 2.0 definition of clients

Question

I am developing a REST based API for our system. We are going to have several types of clients:

• Web browsers - those will be accessing our API after loading an HTML5 app
• Mobile apps developed by us
• Mobile apps developed by 3rd parties

I wanted to ask what strategy should we use in defining clients. E.g.

• is each user in our system required to be defined as a client as they need to be authenticated or is the web client considered to be one client?

• do we assign a client to our iPhone app and another to our android app?

• does each 3rd party developer using our API get a separate client id?

Thanks,

Assaf

Answer 1

Visit the Google API console, create a project. Then visit the API Access menu to create a client id. You will see what data is required for different client types, including Web applications, Android and iPhone applications. It might help in figuring out your own requirements.

Here is a screenshot: