Swashbuckle.AspNetCore | Swagger tools for documenting API 's built on ASP.NET Core | REST library

When I request any API endpoint from Swagger UI give me the following error

System.InvalidOperationException: No authenticationScheme was specified, and there was no DefaultChallengeScheme found. The default schemes can be set using either AddAuthentication(string defaultScheme) or AddAuthentication(Action configureOptions).

at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)

at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)

at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)

at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)

at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)

at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

HEADERS

=======

Accept: /

Accept-Encoding: gzip, deflate

Accept-Language: en-US,en;q=0.5

Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJVc2VySWQiOiIzIiwiTG9naW5JZCI6ImFkbWluIiwiVXNlclR5cGVJZCI6IjEiLCJFbWFpbCI6ImEiLCJNb2JpbGUiOiJhIiwianRpIjoiMWU1MDY3ODAtMWRjNS00MDYzLWFkMTktMDdlMjg4MzAxOWVjIiwiZXhwIjoxNjIzNDYzNjQ4LCJpc3MiOiJlZHVjYXJlLmNvbSIsImF1ZCI6ImVkdWNhcmUuY29tIn0.G2-D_oIdwUDw_3iz87jxWBIMabFpLlR5ASjCr109kNM

Connection: keep-alive

Host: localhost:21068

Referer: http://localhost:21068/swagger/index.html

the Swagger configuration is given below

We have a Web API with ~150 controllers (~500 methods) which we upgraded from Core2.2 to net5.0 and along with it we upgraded the Swashbuckle package.

The old version of Swashbuckle used SwaggerResponse attribute to display information on SwaggerUI and we used it heavily over our ~500 methods.

At some point the SwaggerResponse attribute was deprecated and the recommended solution is a different approach: https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/159

Is there a way to

• either use the SwaggerResponse attribute in latest Swashbuckle, or
• convert the existing code?

I have Blazor Webassembly ASP.NET Core hosted and I installed Swashbuckle.AspNetCore to display endpoints that my Blazor app has (/swagger endpoint).
My Startup.Configure looks like this (only swagger part):

I'm using Swashbuckle.AspNetCore.Swagger to generate a swagger document and then using NSwag to generate a C# SDK.

I have a couple classes where I use a Dictionary to hold miscellaneous properties.

I'm using Swashbuckle to implement an OpenAPI documentation for my web api. I have decided to use a [SwaggerOperationFilter] attribute in one of my operations in order to improve its Response Body example.

According to the documentation, Swashbuckle's filter pipelines can use Dependency Injection, as per the following exerpt:

NOTE: Filter pipelines are DI-aware. That is, you can create filters with constructor parameters and if the parameter types are registered with the DI framework, they'll be automatically injected when the filters are instantiated

Here's a simplified version of a controller

I am having an issue with OpenApi json data validation. Based on the OpenApi validation (or editor.swagger.io) my JSON file has unused models. I am supposed to get rid of the warnings and almost all of them comes from System.Reflection Namespace.

Example:

I use EF Core 3.1 and this is my code:

I have 3 Project:

• API Project > Which includes Controller
• DataLayer Project > Which includes my Repository, Interface, ADO.NET Entity, Context.(Class Library Template .NET Framwork)
• Services Project > Which includes my Services, Interface, you can say Business Logic.(Class Library Template .NET Framwork)

So My API Project(Controller) will call Services(Business Layer) then DataLayer Project(DbContext).

Microsoft Visual Studio Community 2019 Version 16.9.4 Windows 10 Pro

Any clue why I cannot see the Controllers menu item? This is the Asp.net core 5.0 Web API project

MS Doc says this: https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-5.0&tabs=visual-studio#scaffold-a-controller

But I cannot see that?

New items has this:

Update

CinamaApi.csproj