Subjecting part of my parse.com api to other developers via ouath 2.0

Question

Now it’s trivial to create a web application located on Parse.com. Now that I have this webapp, I want to expose part of it to other developers using the oauth accesible api. Thus, they can develop an application that allows site users to give them permission through oauth, and now they can access the api.

How do I start doing this?

Update: after @Mubix's answer, I felt the following clarification would help

I am currently accessing Parse from the server via a REST api to get around any javascript security issues: api keys, etc. Thus, the api will be served by a server other than Parse. In addition, the server code is in javascript / nodejs. I came across https://github.com/jaredhanson/oauth2orize , which seems like a likely candidate, wondered how others are doing it, and if someone really went ahead and integrated Parse access.

Answer 1

Hmmm .. Interesting question!

Legal: First of all, their ToS do not seem to be forbidden by what you are trying to do, but you must read it carefully before you start.

Implementation: Although parsing does not provide functions for creating your own APIs, you can implement something yourself. You can consider third-party developers as users of your application. And you can use ACLs for access control.

Problems:

• I see no way to implement oAuth fully in parsing.
• How will third-party applications access your API? Ideally, you would like them to use the REST interface, but with the parse.com REST API, you cannot control access to different parts of your data.

Conclusion: It seems that there are too many problems for implementing the API entirely within the scope of parsing. I would suggest that you write a thin API layer that takes care of auth and uses parsing as the backend. You can use one side of the libraries service available for parsing. eg. PHP library , Node Analysis .