Inso doesn't pickup inherit from parent authentication

[ywidiastuti]

Expected Behavior

Inso should pick up the inherit from parent authentication

Actual Behavior

Inso doesn't pickup inherit from parent authentication

Reproduction Steps

1. Go to inso shell and execute test script which contains inherit from parent authentication
2. Authentication is not picked up from the parent request
3. This works properly if test is executed from Insomnia app

Is there an existing issue for this?

• I have searched the issue tracker for this problem.

Additional Information

No response

Insomnia Version

9.3.0

What operating system are you using?

Ubuntu

Operating System Version

Linux Mint 21.3

Installation method

download from insomnia.rest

Last Known Working Insomnia version

[jackkav]

Thanks for the report. We're currently working a bunch of inso change, please bear with us.

[fabianfiorotto]

I have the same problem. The authentication works for a few minutes. Then it stops working but it starts working again when I clone the request (but just in the cloned request).

[StellaAlexis]

Also encountering this issue on the MacOS app. Insomnia version 9.3.3.

[rni063]

Have the same problem in the API client. If I switch to another test environment, and refresh the parent authentication, it will still use the old/previous token. Clearing and refetching the token has no effect.

However, if I duplicate the failed request, the new copy will inherit and use the new authentication from parent.

As it is quite annoying to duplicate 20 request for every single staging environment, I hope for a fix soon

[serkan-lx]

Same for me on the macOS app Version 10.0.0

[OssamaSijbesma]

Same MacOS v10.0.0

Any updates, regarding this issue?

Also when you set OAuth 2.0 manually and then switch back to Inherit from parent, it works for that specific request. Even after deleting all cookies, clearing OAuth 2 session, and clearing the token. So I suspect that the auth selection menu might be broken as it is probably still using the manually set authentication in the background.

[jackkav]

Its related to the statefulness of oauth2 tokens compared to other auth methods which don't have a token persistence step.
I think it would be helpful for dx and ux to raise a valid fetched oauth2 token to somewhere higher in the UI than it currently is. I'm thinking perhaps a hover over the auth tab could show key expiry or something. That way it would be clearer if a key is resolved and its state, when inheriting a token.