3.x authorizations are applied to operation, not client

[fehguy]

This was an unintended change from the 2.x series for swagger-js, we should be able to authorize a client and have it apply them to operations as needed. Instead, we have to apply them to each operation, every time.

[ponelat]

see: swagger-api/swagger-ui#2793

[webron]

@ponelat does #975 cover this and the issue can be closed or is something else needed?

[ponelat]

Yup that solves this issue. It doesn't solve the issue of adding auth to fetching the spec. That's tracked elsewhere.

[jasongonzales23]

Hi, I got here from the FAQs, and it looks like you've changed how authorizations worked. If that is correct, perhaps we should document this. Happy to help, BTW, but perhaps someone with more experience with the project can do it better than I.

[komasoftware]

I have a Swagger 2.0 spec with following security definition

securityDefinitions:
    jwt:
        type: apiKey
        name: Authorization
        in: header

But I have a hard time getting the swagger-js 3.0 client to pass the credentials.
This is what I am doing

            let authorizations = {
                jwt: { token: { access_token: "jwtvalue goes here" } }
            };
            return new SwaggerClient({
                url: 'specURL goes here',
                authorizations: authorizations
            })
                .then(client => {
               .....

Can I even use the swagger-js 3.0 client against a swagger 2.0 spec ?
The only documentation I could find was in the migration doc ...

[vukee]

Same issue here. I can add whatever I want into 'authorizations', nothing is passed with the request.

Is there somewhere a full documentation for swagger-js? Or some examples how to use authorizations? Would be really helpful.

[devth]

It's still not clear to me how to add per-request operations. All the examples in the index-authorizations tests seem to be global to the client.

[syntax-e]

From the documentation I'm having a pretty tough time understanding how to add the following header to my requests:
authorization: bearer {token}

Any tips?

[gpineda-dev]

It's still not clear to me how to add per-request operations. All the examples in the index-authorizations tests seem to be global to the client.

I encounter the same issue but i solved it with

Swagger(SWAGGER_ENDPOINT,{
    authorizations: {
        accessTokenAuth: `Bearer ${SWAGGER_TOKEN}`
        //accessTokenAuth: {token: {access_token: SWAGGER_TOKEN}}
    }
})

and it works but not very clean
I hope it might help you