Currently in Insomnia, when an Authentication method is choosen for a request, this Authentication method along its associated parameters are persisted only for this said request.
When switching to another request, we have to perform the exact same manual actions to make the Authentication to work.
Suggestion: Like in Postman, make the Authentication method and parameters to be used by all requests.
Use case: APIs (workspace) having way too many requests to be edited one by one.
Can you explain how this works in Postman? I thought they also did it on a per-request basis.
FYI issue was actually discussed before in #330. The proposed solution (parent requests) was abandoned but I think this issue is worth revisiting since it's a common request.
Well the use case I described above was wrong, I edited my message.
I read #330, it looks like a bit hard to implement in Insomnia IMHO. But it would be great too.
But of course I can describe how Postman works, looks simpler than #330: let's say you opened a request named A. You set authentication method to e.g OAuth 1.0 with the proper parameters. You make things with this request, then open another request named B. The authentication method along its parameters will be already set. You then disable authentication in any of these requests: both requests will no more use any authentication.
It's kinda like an authentication shared by every requests in the workspace. It's would be useful as hell because when working with an API on a daily basis with several kind of authentication and with a bunch of requests, it's a pain to update each authentication method for each requests.
Not sure if I'm explaining well 馃
Related: #781
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.
Please reopen this feature request as I consider it very helpful.
Redirecting all further discussion to a more recent thread here: https://github.com/getinsomnia/insomnia/issues/1116
Most helpful comment
Please reopen this feature request as I consider it very helpful.