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

[Bug] OAuth Authorization data is not stored per environment #1604

Closed
crtl opened this issue Jul 15, 2019 · 4 comments
Closed

[Bug] OAuth Authorization data is not stored per environment #1604

crtl opened this issue Jul 15, 2019 · 4 comments
Labels
stale Bot: Stale Issue

Comments

@crtl
Copy link

crtl commented Jul 15, 2019

  • Insomnia Version: 6.5.4
  • Operating System: Windows 10 Home

Details

Steps to reproduce

  1. Setup request with OAuth 2 authorization
  2. Request access/refresh tokens
  3. Switch environments
  4. Tokens are not cleared, requests are unauthorized

When using OAuth2 for authorization and switching environments the access/refresh tokens are not cleared. I have to manually clear/refresh them when switching environments.

I have only tested this with OAuth2.

In my opionion access tokens should be stored/cleared per environment, because environents are normally used to configure production and dev servers in the workspace and therefore normally never share authorization credentials.

@welcome
Copy link

welcome bot commented Jul 15, 2019

👋 Thanks for opening your first issue! If you're reporting a 🐞 bug, please make sure
you include steps to reproduce it. If you're requesting a feature 🎁, please provide real
use cases that would benefit. 👪

To help make this a smooth process, please be sure you have first read the
contributing guidelines.

@pathawks
Copy link

I would also like to use different OAuth credentials in different environments.

@stale
Copy link

stale bot commented Oct 26, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Bot: Stale Issue label Oct 26, 2019
@stale stale bot closed this as completed Nov 2, 2019
@gschier
Copy link
Contributor

gschier commented Dec 12, 2019

Duplicate of #260

@gschier gschier marked this as a duplicate of #260 Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Bot: Stale Issue
Projects
None yet
Development

No branches or pull requests

3 participants