Kong / Kong/insomnia

Failed to Render when token refresh fails

Open
#6,344 0 comments 0 reactions 0 assignees View on GitHub
B-bug S-unverified
Dominant language
TypeScript
Stars
40k
Forks
2.4k
Avg merge
2d 13h
Merged PRs (30d)
61

Description

### Expected Behavior

When I send a request with an old OAuth token, whose refresh token has expired, I expect Insomnia to fail to refresh the token and not be able to send the request.

### Actual Behavior

Insomnia failed to refresh the token and then an application error occurs.

![image](https://github.com/Kong/insomnia/assets/140202715/58747cee-03a7-43d1-8f4f-13e279983be7)

### Reproduction Steps

1. Create a request with an OAuth 2 token
2. Wait for the refresh token to expire
3. Send a request

### Is there an existing issue for this?

- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Additional Information

_No response_

### Insomnia Version

2023.5.5

### What operating system are you using?

Windows

### Operating System Version

Windows 11, 21H2

### Installation method

Download

### Last Known Working Insomnia version

This was working a few weeks ago

Contributor guide

Open the contributing guide

Research direction

No file or test is named in the report. Start by reproducing the OAuth 2 request flow on Windows with an expired refresh token, then trace the token-refresh failure to the application error. Done means the request is refused cleanly without an application error when refresh fails.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.