Hi, yes, you would create multiple securityDefinition objects--see here for details <https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#securityDefinitionsObject> on that structure.
Then, on each operation that is secured, assign the required security, which references your security definitions. There is an example in the http://petstore.swagger.io/v2/swagger.json application. On Sunday, October 23, 2016 at 2:00:20 AM UTC-7, Tamer Shahin wrote: > > I'm quite interested in this as well! > > is there any way (within the same swagger file) to create a set of basic > endpoints available as open/public API and a superset for private/internal > use only. > > Thanks! > > > Il giorno giovedì 20 ottobre 2016 18:30:11 UTC+1, Diff ha scritto: >> >> In my API documentation, I would like to define the security necessary >> for each API endpoint. The project has defined roles and permissions that >> determine which users can access the APIs. What is the best way in Swagger >> to document this information? I researched the option of using >> securityDefinitions and using a self-defined variable for the roles, but >> that information didn't get copied over into the documentation when I ran >> it through swagger2markup or using the Swagger UI. Is there a best >> practice or recommendation on how to show this detail? >> > -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
