I'm developing an application on .NET Core 3.1 + Angular and everything was working fine until recently, when I was trying to implement Negotiate Authentication configuration to the backend. Anyway the issue persists even after reverting all the Authentication configuration so it may not be related.
I'm getting CORS error with description PreflightMissingAllowOriginHeader followed by 401 error.
Below you can see my code. Out of frustration I have even allowed all origins, headers and methods, when I was trying to debug this issue.
Startup.cs
public void ConfigureServices(IServiceCollection services)
{
services.AddCors(options =>
{
options.AddPolicy(name: MyAllowSpecificOrigins,
builder => { builder.AllowAnyOrigin().AllowAnyHeader().AllowAnyMethod().AllowCredentials(); });
});
// Tried both ^ and v
/* services.AddCors(options =>
{
options.AddPolicy(name: MyAllowSpecificOrigins,
builder => { builder.WithOrigins("http://localhost:4200").AllowAnyHeader().AllowAnyMethod().AllowCredentials(); });
});*/
.
.
.
.
services.AddAuthentication(NegotiateDefaults.AuthenticationScheme).AddNegotiate();
.
.
.
.
.
}
public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
/* app.UseHttpsRedirection();*/
app.UseRouting();
app.UseCors(MyAllowSpecificOrigins);
app.UseAuthentication();
app.UseAuthorization();
app.UseEndpoints(endpoints =>
{
endpoints.MapControllers().RequireCors(MyAllowSpecificOrigins); // <--- Tried both with and without RequireCors
});
}
Angular WebReqService
readonly ROOT_URL: string;
readonly httpHeaders: HttpHeaders = new HttpHeaders({'Content-Type': 'application/json'});
readonly httpOptions = {
headers: this.httpHeaders,
withCredentials: true
};
constructor(private http: HttpClient) {
this.ROOT_URL = 'http://localhost:5000';
}
get(uri: string): Observable<any> {
return this.http.get<any[]>(`${this.ROOT_URL}/${uri}`, this.httpOptions);
}
The strangest about it is that if I try to access the API directly by calling the request in browser or in Insomnia with NTLM Authorization, everything works just fine. Only if I try to access the API from Angular FE, I get the error.
Any ideas what could be the cause and how to fix it? Also, I think that it's not caused by not being authorized to use the application, because as I said it works outside the Angular and also if user is not authorized, it's configured to return 403 instead of 401.
