[CC API] OAuth2 support on the backend about cccatalog-api HOT 3 CLOSED

Using GitHub users can work pretty well, also.

@aldenstpage, what do you think?

from cccatalog-api.

I like the suggestion to use GitHub accounts. I don't want to link it up to CCID since it sounds like nobody wants to maintain it and because API authorization should be managed separately from end-user application authorization.

from cccatalog-api.

I added support for two OAuth2 authorization flows:

1. For push API users: We issue a client id and client secret to whoever wants access to our API. Using those details, they request a temporary bearer token from our API server. There is no third party for this flow; everything happens on our servers.
2. GitHub social login for front-end users. We should support more options later, since most end users will not be developers. It is relatively easy to add a new social backend as long as it's supported by python-social-auth.

from cccatalog-api.