Resolver error at ... Could not resolve reference because of: Unauthorized

[dylancwood]

• swagger-ui-dist version v3.0.13

Our server uses http-basic authentication to protect our API docs (for some reason that I don't understand). Once a user logs in, the browser will send the appropriate authorization header with all requests for JS, CSS, XHR, images, etc... The swagger-ui renders quite well, except that it has a giant red error message on top stating the following:

Errors:
Resolver error at definitions.status.$ref
Could not resolve reference because of: Unauthorized
Resolver error at definitions.supportedStoresData.$ref
Could not resolve reference because of: Unauthorized

This is due to a 401 response when trying to retrieve definitions.json.

Looking at the network panel of Chrome dev tools, I see that the core JSON swagger file was fetched via XHR using the HTTP authorization headers as expected. However, the request to get definitions.json did not include any authorization headers.

(Above: Network request to get core swagger.json file)

(Above: Network request to get definitions.json file)

Thanks in advance for any advice.

[shockey]

Is this what you're looking for? #2793

[dylancwood]

@shockey: Thank you, I had not seen that issue. It sounds like there is a work-around, but I don't see why that should be necessary. When someone authorizes (enters username/pwd) using the browser's built-in http-basic auth system, then the browser will send the authorization header on all future requests to the same protocol/domain/port. This is how swagger-ui is able to load all the assets (js, css, ajax, etc...) without re-prompting for a password each time.

There must be something special about the way definitions are retrieved that is causing the browser to omit authorization headers.

[shockey]

@dylancwood, I'm inclined to say that your PR last week (referenced above this comment) solves this 😄 Am I correct?

[shockey]

Closing due to inactivity.

This is simply to keep our issue tracker clean - feel free to comment if there are any further thoughts or concerns, and we'll be happy to reopen this issue.

[anjukuriakose]

Hi,

Getting the same error.

In swagger, its validating . Please help me on this.

[shockey]

@anjukuriakose, it appears that your $refs are missing a # at the beginning of their values - it should be #/definitions/MathResourceList, not /definitions/MathResourceList.