APIs Beta Generate Collection sets Authorization on all request to "No Auth"

Describe the bug When an API is imported through the APIs^Beta interface, then the ‘Generate Collection’ button is clicked, all requests in the resulting Collection have their ‘Authorization’ set to ‘No Auth’. This is true even if security and/or securitySchemes are set in the OpenAPI schema. This makes it difficult to set the ‘Authorization’ for all Requests in a Collection. It seems like it would make more sense to default ‘Authorization’ to ‘Inherit auth from parent’.

To Reproduce Steps to reproduce the behavior:

1. Go to ‘APIs^Beta’
2. Click on ‘New API’
3. Click on ‘Add Schema’
4. Import an OpenAPI schema
5. Click on ‘Save’
6. Click on ‘Generate Collection’
7. Go to ‘Collections’
8. Go to the generated collection
9. Go to any request in the collection
10. Go to ‘Authorization’
11. See that ‘Type’ is set to ‘No Auth’

Expected behavior The ‘Type’ should be set to ‘Inherit auth from parent’ or utilize the security and/or securitySchemes properties in the OpenAPI schema.

App information (please complete the following information):

• App Type: Native App
• Postman Version: 7.1.1
• OS: Windows 10

[jez9999]

@umeshp7 This behaviour still isn’t useful to me - most of my endpoints do indeed specify an OAuth2 bearer token security scheme. This means that most of my endpoints are still generated with “bearer token” as the auth, and no token set by default. For each endpoint I have to manually set the token. There needs to be some way of just always inheriting auth from parent. If anything, it would be more useful to me to inherit auth from parent when a path does have a security scheme defined, and set to “no auth” if there isn’t one defined.

[jez9999]

I’ve just come across this bug too. It’s absurd; inherit from parent is meant to be the default for a reason. Why on earth would you set the default to no auth? If an API requires authentication that’s going to be extremely inconvenient.