Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OAuth 2.0 Token shared between folders #4396

Open
2 of 4 tasks
TheBlackReverand opened this issue Apr 1, 2025 · 1 comment
Open
2 of 4 tasks

OAuth 2.0 Token shared between folders #4396

TheBlackReverand opened this issue Apr 1, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@TheBlackReverand
Copy link

I have checked the following:

  • I have searched existing issues and found nothing related to my issue.

This bug is:

  • making Bruno unusable for me
  • slowing me down but I'm able to continue working
  • annoying

Bruno version

2.0.1

Operating System

Windows 11 Professionnal 23H2 build 22631.5039

Describe the bug

I have one collections with 2 folders.

Each folder have an OAuth 2.0 authentification.

Folder A have a token without scope.
Folder B have a token with scope.

Each folder have requests, sometimes a request can be on the folder A and B.

I start a request from the folder A, a token without scope is generated and request return HTTP 200 => perfect
I start a request from the folder B, Bruno use the same token, so request return HTTP 401 - need scope => bad

If I go in folder B and make "Get Access Token", I get a token with scope and now request return HTTP 200.
After that all request from folder A have scope.

Thanks for this feature,
Good luck for fix.

.bru file to reproduce the bug

No response

Screenshots/Live demo link

no screenshot / demo, too many sensive data on screen

@TheBlackReverand TheBlackReverand added the bug Something isn't working label Apr 1, 2025
@anusree-bruno
Copy link
Collaborator

Could you try using a different Token ID in this scenario?

If you use the same Token ID with the same auth URL, the tokens will be replaced. Since you need to keep the same URLs, using a different Token ID will allow you to store multiple tokens separately.

Image

@anusree-bruno anusree-bruno self-assigned this Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants