[GH-ISSUE #1011] API token deletion not reflected in cache until page reload

kerem commented

2026-02-26 18:46:25 +03:00

Owner

Originally created by @ashrafchowdury on GitHub (Mar 9, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1011

Issue Description

After deleting the API token, the token still persists in the cache. Despite the deletion process, the token remains accessible until the page is manually reloaded. This inconsistency poses a potential security risk.

Also, the 'Token expiration date' field is not clear after successfully creating the API token.

Steps to Reproduce

Log in to the app,
Navigate to the settings or profile section where API tokens are managed.
Create a new API token.
Then delete that API token.
Notice that the deleted token is still accepted and functional.
Manually reload the page to remove the token from the display

Expected Behavior

The API token should be immediately removed from the cache after successfully deleting it from the database.

Current Behavior

The API token remains accessible and functional even after deletion until the page is manually reloaded.

Screenshots (optional)

https://github.com/documenso/documenso/assets/87828904/187c5565-d2c5-42b0-b698-5c978045076a

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome, Edge

Version [e.g., 2.0.1]

Latest

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @ashrafchowdury on GitHub (Mar 9, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1011 ### Issue Description After deleting the API token, the token still persists in the cache. Despite the deletion process, the token remains accessible until the page is manually reloaded. This inconsistency poses a potential security risk. Also, the 'Token expiration date' field is not clear after successfully creating the API token. ### Steps to Reproduce 1. Log in to the app, 2. Navigate to the settings or profile section where API tokens are managed. 3. Create a new API token. 4. Then delete that API token. 5. Notice that the deleted token is still accepted and functional. 6. Manually reload the page to remove the token from the display ### Expected Behavior The API token should be immediately removed from the cache after successfully deleting it from the database. ### Current Behavior The API token remains accessible and functional even after deletion until the page is manually reloaded. ### Screenshots (optional) https://github.com/documenso/documenso/assets/87828904/187c5565-d2c5-42b0-b698-5c978045076a ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Chrome, Edge ### Version [e.g., 2.0.1] Latest ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [X] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [X] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [X] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:46:25 +03:00

closed this issue
added the
type: bug

status: assigned

apps: web

component: ui
labels

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ashrafchowdury commented on GitHub (Mar 9, 2024):

I would like to work on this issue if it gets approved.

@ashrafchowdury commented on GitHub (Mar 9, 2024): **I would like to work on this issue if it gets approved.**

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@dguyen commented on GitHub (Mar 13, 2024):

Thanks, assigned it to you :)

@dguyen commented on GitHub (Mar 13, 2024): Thanks, assigned it to you :)

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@SaiSawant1 commented on GitHub (Mar 27, 2024):

@ashrafchowdury are you working on this?

@SaiSawant1 commented on GitHub (Mar 27, 2024): @ashrafchowdury are you working on this?

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ashrafchowdury commented on GitHub (Mar 28, 2024):

@ashrafchowdury are you working on this?

Yes.

@ashrafchowdury commented on GitHub (Mar 28, 2024): > @ashrafchowdury are you working on this? Yes.

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@rushatgabhane commented on GitHub (Apr 24, 2024):

Hey, @ashrafchowdury it's been almost two months since you were assigned. How's it looking? Do you need help?

@rushatgabhane commented on GitHub (Apr 24, 2024): Hey, @ashrafchowdury it's been almost two months since you were assigned. How's it looking? Do you need help?

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@rushatgabhane commented on GitHub (Apr 24, 2024):

I'd love to work on this issue if that's okay. I aim to complete it in 3 days

@rushatgabhane commented on GitHub (Apr 24, 2024): I'd love to work on this issue if that's okay. I aim to complete it in 3 days

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 25, 2024):

@ashrafchowdury are you actively working on this? Otherwise I'm reassigning tomorrow..

@ElTimuro commented on GitHub (Apr 25, 2024): @ashrafchowdury are you actively working on this? Otherwise I'm reassigning tomorrow..

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ashrafchowdury commented on GitHub (Apr 26, 2024):

@ashrafchowdury are you actively working on this? Otherwise I'm reassigning tomorrow..

I'm really sorry for the late reply @ElTimuro, I not working on this issue currently feel free to assign someone else.

Again, I apologize for not taking any action on it.

@ashrafchowdury commented on GitHub (Apr 26, 2024): > @ashrafchowdury are you actively working on this? Otherwise I'm reassigning tomorrow.. I'm really sorry for the late reply @ElTimuro, I not working on this issue currently feel free to assign someone else. Again, I apologize for not taking any action on it.

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 26, 2024):

@rushatgabhane afaik you have another issue, you want to take this one as well? Please be mindful if 2 in parralel are too much :D

@ElTimuro commented on GitHub (Apr 26, 2024): @rushatgabhane afaik you have another issue, you want to take this one as well? Please be mindful if 2 in parralel are too much :D

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 26, 2024):

@ashrafchowdury it's fine, thanks for letting me know

@ElTimuro commented on GitHub (Apr 26, 2024): @ashrafchowdury it's fine, thanks for letting me know

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@cchirag commented on GitHub (Apr 29, 2024):

Can I work on this?

@cchirag commented on GitHub (Apr 29, 2024): Can I work on this?

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 29, 2024):

@cchirag if @rushatgabhane declines you can have it
@rushatgabhane, since you asked first, do you still want to do this?

@ElTimuro commented on GitHub (Apr 29, 2024): - @cchirag if @rushatgabhane declines you can have it - @rushatgabhane, since you asked first, do you still want to do this?

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@cchirag commented on GitHub (Apr 29, 2024):

Cool @ElTimuro . Let me know if @rushatgabhane chooses to decline. Thank you.

@cchirag commented on GitHub (Apr 29, 2024): Cool @ElTimuro . Let me know if @rushatgabhane chooses to decline. Thank you.

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@rushatgabhane commented on GitHub (Apr 30, 2024):

@ElTimuro i was interested, but it looks like @cchirag already raised a PR 😅
So maybe we just assign them, what do you think?

@rushatgabhane commented on GitHub (Apr 30, 2024): @ElTimuro i was interested, but it looks like @cchirag already raised a PR 😅 So maybe we just assign them, what do you think?

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@cchirag commented on GitHub (Apr 30, 2024):

Hey @rushatgabhane, sorry for picking up the task. The fix seemed straightforward and we had not heard from you in 4 days. But, I guess you can review my PR and maybe share it with us if you have a better approach.

@cchirag commented on GitHub (Apr 30, 2024): Hey @rushatgabhane, sorry for picking up the task. The fix seemed straightforward and we had not heard from you in 4 days. But, I guess you can review my PR and maybe share it with us if you have a better approach.

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@rushatgabhane commented on GitHub (Apr 30, 2024):

@cchirag don't worry about it, it's all good : )

@rushatgabhane commented on GitHub (Apr 30, 2024): @cchirag don't worry about it, it's all good : )

kerem commented

2026-02-26 18:46:26 +03:00

Author

Owner

@cchirag commented on GitHub (Apr 30, 2024):

Thanks man @rushatgabhane . @ElTimuro can you please review the PR.

@cchirag commented on GitHub (Apr 30, 2024): Thanks man @rushatgabhane . @ElTimuro can you please review the PR.

kerem referenced this issue

2026-02-26 19:30:48 +03:00

[PR #308] [MERGED] feat: pr title validator workflow #863

Rows
Columns

[GH-ISSUE #1011] API token deletion not reflected in cache until page reload #308

Issue Description

Steps to Reproduce

Expected Behavior

Current Behavior

Screenshots (optional)

Operating System [e.g., Windows 10]

Browser [e.g., Chrome, Firefox]

Version [e.g., 2.0.1]

Please check the boxes that apply to this issue report.