Add a way to define authentication at the collection level

[duraz0rz]

I know folder-level auth is a thing, but it would be nice to be able to define authentication for the whole collection.

I don't think folder-level authentication really fits the case for a single API that can change freqeuently. When I create a collection from an OpenAPI spec, I then have to move all of those endpoints into a parent folder in order to share the same auth method. When I reimport the spec after changes are made, I have to delete the old endpoints from the folder and then move the new endpoints into the folder.

[poojithap11]

Hi,

Thank you for your feedback.

You can use environment variables to help centralize credentials at the collection-level. You can define your API keys, token or credentials as environment variables, and then reference them in your requests using ({{ variable_name }}.

Could you clarify if this approach would meet your requirement? Understanding this will help us capture the use case accurately.

[duraz0rz]

I already have credentials set up and using them in other collections fine, but setting up an authentication method for a collection require a top-level folder in order to do so.

If you import an OpenAPI specification (like a swagger.json or something), you have to create a top-level folder and move all of the endpoints into that folder. If the swagger.json changes and you re-import, the top-level folder is deleted and you have to do this again.

If I can set up an authentication method at the collection level instead of requiring a top-level folder, that would alleviate some pain in importing OpenAPI specifications.

[poojithap11]

Hi, A feature request has been raised to add collection-level authentication for API's in insomnia.