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

Credentials Location not saving #470

Open
theOriginalLoopback opened this issue May 19, 2022 · 0 comments
Open

Credentials Location not saving #470

theOriginalLoopback opened this issue May 19, 2022 · 0 comments
Labels

Comments

@theOriginalLoopback
Copy link

When configuring a new request, using OAuth 2 authorization, under Advanced Settings, the Credentials Location setting defaults to "Message Body". I change that to "Authorization Header", and save the request.

When I open the request again, the Credentials Location has defaulted back to "Message Body".

Expected outcome

User-selected value should be retained.

Actual outcome

Drop-down defaults back to "Message Body"

Versions

App: 17.0.9
Platform: win32
Electron: 17.1.0
Chrome: 101.0.4951.54
V8: 9.8.177.11-electron.0
Node: 16.13.0

Steps to reproduce

  1. Create new request
  2. Select "Authorization" tab
  3. Enable "OAuth 2" entry under "Select authorization" drop-down
  4. Select OAuth 2 entry under "Select authorization" drop-down to change view
  5. Select "Client Credentials" under "Grant type" drop-down
  6. Enter Client ID
  7. Enter Client Secret
  8. Enter Access Token URI
  9. Add "api" to the Scopes collection
  10. Select "Authorization Header" under "Credentials location" drop-down
    Screenshot 2022-05-19 150143
  11. Save request
  12. Clear the editor
  13. Open previously saved request
  14. Select "Authorization" tab
  15. Enable "Advanced settings" toggle
  16. Observe "Credentials location" setting has reverted to "Message body"
    Screenshot 2022-05-19 150007
@jarrodek jarrodek added the bug label May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants