Content
View differences
Updated by Wieland Lindenthal over 3 years ago
**As** a user
**I want to** have a simple way to cut the connection between OP & NC
**so that** I don't forget to do only part of the process
**Acceptance criteria**
* Removing removing the connection on one side (here in this WP we focus on the Nextcloud side) (NC or OP) also disconnects the other side.
side
**TODO:**
* Delete client tokens received from [ ] find or implement an endpoint to delete the other current oauth token of a user on OP side
* Revoke client tokens received from [ ] find or implement an endpoint to delete the other current oauth token of a user on NC side
* Delete client tokens that were provided for [ ] when a user disconnects in OP notify NC to revoke the other side
**Notes:**
To revoke a OAuth client token of of that was provided by OpenProject there is user
* [ ] when a special endpoint to POST to. See documentation here [https://github.com/doorkeeper-gem/doorkeeper/wiki/API-endpoint-descriptions-and-examples#post---oauthrevoke](https://github.com/doorkeeper-gem/doorkeeper/wiki/API-endpoint-descriptions-and-examples#post---oauthrevoke)
There is currently no endpoint user disconnects in Nextcloud NC notify OP to revoke tokens. So we would need to implement that functionality ourselves. However, I don't believe that this is a wise idea. In my opinion that is a missing feature in the Nextcloud core. <mention class="mention" data-id="74290" data-type="user" data-text="@julien.veyssier @nextcloud.com">@julien.veyssier @nextcloud.com</mention> could you please provide a feature request against Nextcloud core and link OAuth token of of that request here? We can always consider implementing that as a Nextcloud core feature. user
**I want to** have a simple way to cut the connection between OP & NC
**so that** I don't forget to do only part of the process
**Acceptance criteria**
* Removing
**TODO:**
**Notes:**
To revoke a OAuth client token
* [ ] when
There is currently no endpoint