Feature proposal #5813
24 February 2016
Implement support for CB Connect to act as a provider. Generating client id and secret on 1 site that can be put on another. The endpoints would be CB Connect. This needs to be able to support multiple sites.
Needs a component page for a user to view authorized applications so they can be revoked.
Needs at least 2 database tables. 1 for storing user authorized apps and 1 for handling ID, User ID, Date, Code, Access Token (for that code), and Expires storage (adjust columns as needed).
Use endpoints similar to endpoint.php with authorize.php, access_token.php, and api.php (direct component view URL will work too, but these endpoints make it easier)
Only API usages for the time being will be ?request=me and ?request=user&user=# (request is subject to change)
Also available in: Atom