Added failsafe check for Swaggers with no security definitions

[six2dez]

When a swagger file does not provide a security definition the tool crashes, now it gives a warning and continues

The error before the fix:

After the fix:

[twest-bf]

I'm having trouble reproducing this against a file that does not define a security scheme.

The following lines in auth.go should already cover cases where a security definition is not provided:

// line 27
if len(doc3.Components.SecuritySchemes) != 0 {
...SNIP...
// line 35
if len(doc3.Components.SecuritySchemes) > 0 {

Are you able to provide a definition file to test against as well as the version of sj and the command that returns the error?

[six2dez]

Yes, sure! I was testing with this swagger definition
swagger - Copy.json