# Feature NEX-685 - [backport] Do not revoke access tokens and let OpenProject handle the revocation

Project: Stream Nextcloud app "OpenProject Integration"
Status: closed
URL: https://community.openproject.org/work_packages/NEX-685

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions |  Nextcloud Integration 2.12.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

Do not revoke the access tokens received from OpenProject for each connected Nextcloud user, but instead let OpenProject handle it.

User tokens get revoked after resetting or recreating OpenProject client credentials. This can be costly in terms of performance if there are large number for connected Nextcloud users.

**Acceptance criteria**

*   Upon resetting or recreating OpenProject client, token revocation per user doesn't happen.
    

Ref: https://community.openproject.org/projects/NEX/work\_packages/NEX-196/activity#comment-1711084

> As far as I can tell this entire loop-to-revoke is not necessary at all. It only happens in cases where we would expect OpenProject to have revoked the tokens on its own anyways.
> 
> So I think this feature should be rewritten to stop to revocation loop.