Skip to content

[feature]: Authorization setting at Collection level #2259

@minhnguyen-ew

Description

@minhnguyen-ew

Is there an existing issue for this?

  • I have searched the existing issues

Summary

In Postman, you can set up an authorization method at the Collection level and all of the requests in that collection will inherit that authorization method (unless you override that in the endpoints themself). We can try to provide a similar mechanism here.

Why should this be worked on?

This is useful for a collection with many different requests (for example, I am working on one which has nearly 100 requests) so you don't need to set up the same authorization method request by request.

Yes, I acknowledged that we can duplicate an endpoint to create another one. But in my case, I imported my collection from Postman. And since I set up the authorization method at the Collection level on Postman, all the requests in the collection don't have one on their own. That means I will need to go and config the authorization method for each request after importing (which is too much work).

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions