[GH-ISSUE #4391] [bug]: Token generation steps to be executed twice before token is set #1608

New issue

Open

opened 2026-03-16 21:04:21 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 21:04:21 +03:00

Owner

Originally created by @maudidio on GitHub (Oct 1, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4391

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I try to generate a new OAUTH token (authorization set at Collection level) I need to execute token generation steps twice to have the token set properly.

Steps to reproduce

Right click on the Collection
Go to Authorization
Click on Generate token
Click on Save
Try a request: token is not working.
Repeat steps 1-4
Try a request: token is now working.

Environment

Production

Version

Cloud

Originally created by @maudidio on GitHub (Oct 1, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4391 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I try to generate a new OAUTH token (authorization set at Collection level) I need to execute token generation steps twice to have the token set properly. ### Steps to reproduce 1. Right click on the Collection 2. Go to Authorization 3. Click on Generate token 4. Click on Save 5. Try a request: token is not working. 6. Repeat steps 1-4 7. Try a request: token is now working. ### Environment Production ### Version Cloud

kerem added the

bug

need testing

labels

2026-03-16 21:04:21 +03:00

kerem commented

2026-03-16 21:04:32 +03:00

Author

Owner

@MichaMican commented on GitHub (Mar 17, 2025):

I have this problem too with generally all Authentication settings. Even if i set a token "manually" I always have to save the files twice.

@maudidio to verify if this is the same issue - could you try to generate a new token and then instead of regenerating it just open the properties again and immediately klick on save and check if the token works now.

@MichaMican commented on GitHub (Mar 17, 2025): I have this problem too with generally all Authentication settings. Even if i set a token "manually" I always have to save the files twice. @maudidio to verify if this is the same issue - could you try to generate a new token and then instead of regenerating it just open the properties again and immediately klick on save and check if the token works now. ![Image](https://github.com/user-attachments/assets/3d97477a-7336-403f-b722-5509c44c0617)

kerem commented

2026-03-16 21:04:37 +03:00

Author

Owner

@maudidio commented on GitHub (Mar 17, 2025):

@MichaMican thanks for the reply. Yes, it does the same to me: just saving twice makes tokens work.

@maudidio commented on GitHub (Mar 17, 2025): @MichaMican thanks for the reply. Yes, it does the same to me: just saving twice makes tokens work.

kerem referenced this issue

2026-03-17 01:02:37 +03:00

[PR #1608] [MERGED] chore(deps): bump ssri from 6.0.1 to 6.0.2 #3426