Allow inherited authentication that is configured at collection or directory level

[andreassiegel]

When working with different APIs, many (or even all) requests share the same authentication. Right now, it has to be configured for each request individually although all actually require the exact same settings.
These settings, however, are not the same for all requests in all directories in a collection.

For instance, there are APIs that require HTTP Basic Authentication, others use API keys or OAuth 2.0 with client credentials or authorization code flow. Actual credentials might also differ between requests or APIs. So there is quite some variance but still, requests have a lot in common, and some grouping mechanism would be appreciated.

This actually also is an issue with the collection import from Postman as Postman allowed the inheritance of authentication from directories but that information is gone so requests will not work and have to be updated manually.

Therefore, it would be good to be able to set the authentication only once and be able to configure individual requests to either use their own authentication configuration or inherit the configuration from a parent.

This feature request certainly is related to #3694 but in my mind not the same as the other is more getting at environments, and I would like to see that as part of the collection configuration. Also, that discussion is quite old already.

[pczopa]

Migrating from Postman to Insomnia and this is the most annoying thing to have to deal with - would love for this feature to be included in Insomnia!

[subnetmarco]

I am prioritizing this for the April/May timeframe, after the large Insomnia 9.x release we are about to release in March.

[subnetmarco]

This is possible since Insomnia 9.3.

[K3UL]

@subnetmarco this is partially possible. It is now possible to do it at the directory level (which is already a huge improvement, thank you for that).

But it is not possible to do it at the collection level, which means that if I have a collection where the auth is the same, I still have to create a parent directory, just to carry certain settings.

Only a minor inconvenience, but it would be nice to also have the settings on the collection.

[subnetmarco]

I still have to create a parent directory, just to carry certain settings.

Yes, I agree that while this provides a solution, it still requires that parent folder. From a UX standpoint, where do you think we should add these "Collection Level" settings? It's actually not intuitive where it should be.

If it's hidden in this dropdown (where it should naturally be placed), nobody will be able to see it:

Or maybe it can be a default (not removable) element at the top of the list here:

What do you think? @K3UL