Content
View differences
Updated by Wieland Lindenthal about 4 years ago
Given
* a `OAuthClient` that we know is Nextcloud specific
Acceptance criteria:
* Allow adding OAuth2 access tokens for `Storage`.
Implementation ideas:
* Create `OAuthClients::ConnectionManager`
* acts as a base class
* `OAuthClients::ConnectionManagerNextcloud`
* Implements `OAuthClients::ConnectionManager`
* Can create the URL that the user's browser needs to go to so that a user can login and authorize in NC.
* OP core has routes for:
* `OAuthClientsController` with a `callback` that gets called by Nextcloud after authorization by user in Nextcloud. `/auth_client/{oauth_client_id}/callback`
* The controller figures out which connection manager to use and passes the following parameter (scope, code, ... to be completed with OAuth2 standard params)
Out of scope:
* Prepare a registry for OAuthClient specific strategies (Nextcloud, Google drive, ...)
* a `OAuthClient` that we know is Nextcloud specific
Acceptance criteria:
* Allow adding OAuth2 access tokens for `Storage`.
Implementation ideas:
* Create `OAuthClients::ConnectionManager`
* acts as a base class
* `OAuthClients::ConnectionManagerNextcloud`
* Implements `OAuthClients::ConnectionManager`
* Can create the URL that the user's browser needs to go to so that a user can login and authorize in NC.
* OP core has routes for:
* `OAuthClientsController` with a `callback` that gets called by Nextcloud after authorization by user in Nextcloud. `/auth_client/{oauth_client_id}/callback`
* The controller figures out which connection manager to use and passes the following parameter (scope, code, ... to be completed with OAuth2 standard params)
Out of scope:
* Prepare a registry for OAuthClient specific strategies (Nextcloud, Google drive, ...)