Importing A Swagger File To Postman That Requires Authentication

[bhreinb]

trafficstars

Hi there,

I'd like to do REST API testing through postman. Ideally I'd like to import the swagger definition from a URL (as that is the source of truth for our ever evolving set of REST APIs) and let postman convert the swagger definition to a postman collection.

That feature already works in circumstances when the swagger definition can be accessed using anonymous authentication. However, due to security constraints the swagger definition we expose are secured by basic authentication hence importing via dialog "Import From Link" fails for me.

I have tried to evolve the url to include basic authentication namely

https:username:[email protected]

but that doesn't work for me either. It would be great if their was a way to input basic authentication as part of that input interface so importing swagger via a url can work if the swagger url has anonymous or basic authentication. Thoughts?

Thanks in advance.

[bhreinb]

Is their any further progress on this? We can't import a swagger file to postman that is password protected which is a real limitation.

[ChristopherSnay]

I require the same feature. I was surprised there is no way to do this.

[MinghongGao]

same here

[dkarakas1]

+1 to add ability to include auth in the import from link feature.

Further, since authentication for some may be a two step process:

1. Provide Username:Password to fetch a Bearer Token (or whatever)
2. Use Token in authorization header to access api endpoint to download api.json

it would be ideal to have the Import/Link screen allow me the ability to provide the user:pass required to acquire a token, then use that token in the get request for the myapi.json file I intend to import.

Maybe go as far as adding the full 'Authorization', 'Pre-request Scripts', 'Tests', and 'Variables' screens to the Import wizard similar to what is currently available for 'Collections'.

As an request for enhancement however, I would ask that Postman actually decouple the entire 'Authorization', 'Pre-request Scripts', 'Tests', and 'Variables' screens into their own 'Authorizations' object space so they can be managed as grouped collections independently from Collections and allowing them to be defined once and used across multiple collections in addition to the import feature.

Authorizations

• MyAuth1
  • Authorization Method
  • Pre-request Scripts
  • Tests
  • Variables
• MyAuth2
  • Authorization Method
  • Pre-request Scripts
  • Tests
  • Variables

Then let me reference my auth-group and subsequent 'Token' variable within my collections as appropriate.

[harshit-raj]

+1 definitely a very important required feature

[gedankennebel]

+1

[cionz0]

+1

[DjThossi]

+1. I try to import a Pixi WSDL file. This is not working due to basic auth. Please enable either basic auth credentials or even as quick fix to allow to have the credentials in the URL.

[pavlokomarov]

It would be a nice feature for protected APIs

[kishoreankit95]

I have made a detailed video on this. Please check it out and let me know your feedbacks. https://youtu.be/-XPPJyhz93E?si=atLVjZVVDRGtMfSo

[hafsa94]

+1