and or for authentication

[Lehp]

Is your feature request related to a problem? Please describe.
I have to declare multiple possibiliteies of authentication. My Yaml file needs to look like image+ but i don't know if it's possible to configure this.

Describe the solution you'd like
I would like to be able to declare multiple options for a parameter

Describe alternatives you've considered
Using Tag multiple time is not accepted by our tool. like @description test @description test2

[ubogdan]

I never used the Oauth part. Any input is welcome.

@akojo @sdghchj @Nerzal

[sdghchj]

I never used the Oauth part. Any input is welcome.

@akojo @sdghchj @Nerzal

Me too.

[akojo]

I'm a bit late to the game here, but looking at the OpenAPI v2 spec it defines security as being a list of security requirement objects (ORed together), each of which can contain multiple security requirements (ANDed). That is, the most general form for a security requirement would look like:

security:
- BasicAuth: []
  OAuth2Application:
  - write:pets
  - read:pets
- ApiKeyAuth: []

Which would specify one of two authentication options:

• Basic auth and Oauth2 application auth
• API key auth

Considering this it would be best to allow multiple @Security tags to specify a list of security requirement and then additionally some special syntax to handle the rarer cases of ANDing requirements. For the above example swag annotations would then look like:

// @Security BasicAuth && Oauth2Application[write:pets, read:pets]
// @Security ApiKeyAuth

A bit less contrived example: allowing either API key or basic authentication would then be simply

// @Security ApiKeyAuth
// @Security BasicAuth

which would translate to

security:
- BasicAuth: []
- ApiKeyAuth: []

[lucasoares]

Would be nice to be able to configure multiple security tags.

In my use case I need to configure two authentications, both using headers and right now I can't. I created a code to modify the generated json to include my own security definition :(

[Lehp]

I don't know what exactly you want but the "OR" functionality i implemented works like this

So This should be possible:

@akojo @lucasoares

[lucasoares]

I don't know what exactly you want but the "OR" functionality i implemented works like this

So This should be possible:

@akojo @lucasoares

I was having trouble to configure multiple security definitions but now I got it.

The problem I'm having now is to apply the same security for every single handler without the need to copy paste the @Security to each handler.

[bekabaz]

I don't know what exactly you want but the "OR" functionality i implemented works like this
So This should be possible:

@akojo @lucasoares

I was having trouble to configure multiple security definitions but now I got it.

The problem I'm having now is to apply the same security for every single handler without the need to copy paste the @Security to each handler.

Isn't that a bug with the usage of || as an AND? || implies an OR, however that generated swagger doc is in the format of an AND. If I'm wrong I apologize