OAuth2.0 populate `access_token` to env

Is your feature request related to a problem? Please describe. I am using the OAuth2 auth tab and love the tooling around refreshing, adding scopes, encoding helpers.

However for all the other routes - we use Authorization: Bearer #{access_ token} tab like most OAuth2 API’s once the token_set is generated you only need the JWT.

This requires copy & pasting the access_token back into the environment which is shared across my whole workspace and all other API calls.

Describe the solution you’d like I know it is possible to setup OAuth2 flow manually and chain the access_token back into my env var: https://support.insomnia.rest/article/43-chaining-requests - But if we go this route, we loose the convenience of the OAuth2.0 tab refresh & client id/secret helpers.

It would be great to have the ability to set the access_token in the shared environment after a successful access/refresh generation

Describe alternatives you’ve considered Request chaining

Additional context Let me know if this is on the radar, or if there is another workaround I haven’t considered

OA2 helper Tab

Manually refresh and copy paste new token set when you need to interact w/ api

ENV Var

Variable where we store (copy/paste) recently generated access token

Header

All other API requests that don’t need the OA2 tab, but just the Authorization: Bearer #{access_token} header

[dmythro]

Oh, that would be awesome and a completely automated flow for me!

[SerKnight]

Beautiful - Thank you to the developer and for updating the thread…

Note that I did have to change the oA2 token url which is based on the providers token POST base url, not the callabck URL. In my case it matched the alternative example in the readme:

https://identity.xero.com/connect/token so in your environment you put

"oauth2_token_url_suffix": "connect/token"