Reputation: 67
So I have absolutely no idea what happened, but suddenly Swagger became a part of my endpoint URL, meaning it is no longer url.com/api/Values but url.com/Swagger/api/Values. I am unsure of how this happened and I have looked everywhere regarding modifications of base URL etc., but I am sure I just made a tiny mistake somewhere.
Configure()
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseHsts();
}
app.UseSwagger();
app.UseSwaggerUI(c =>
{
c.SwaggerEndpoint("./v1/swagger.json", "LA NOSA - FE API");
});
app.UseDeveloperExceptionPage();
app.UseAuthentication();
app.UseHttpsRedirection();
app.UseMvc();
}
ConfigureServices()
{
services.AddDbContext<DataContext.AppContext>(options =>
options.UseSqlServer(
Configuration.GetConnectionString("DefaultConnection")));
//Register dapper in scope
services.AddScoped<IDapper, DapperManager>();
services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
.AddJwtBearer(options =>
{
options.TokenValidationParameters = new TokenValidationParameters
{
ValidateIssuer = true,
ValidateAudience = true,
ValidateLifetime = true,
ValidateIssuerSigningKey = true,
ValidIssuer = Configuration["Jwt:Issuer"],
ValidAudience = Configuration["Jwt:Issuer"],
IssuerSigningKey = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(Configuration["Jwt:Key"]))
};
});
//services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);
services.AddSwaggerGen(c =>
{
c.AddSecurityDefinition("Bearer", new OpenApiSecurityScheme
{
Description =
"JWT Authorization header using the Bearer scheme. \r\n\r\n Enter 'Bearer' [space] and then your token in the text input below.\r\n\r\nExample: \"Bearer 12345abcdef\"",
Name = "Authorization",
In = ParameterLocation.Header,
Type = SecuritySchemeType.ApiKey,
Scheme = "Bearer"
});
}
Upvotes: 0
Views: 408
Reputation: 113
Check your launchSettings.json may be there is some problem with urls
Upvotes: 1