maxmustermann
/
dotnet-core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

IIS Express issue was fixed

This commit is contained in:
Artak 2021-11-09 15:35:58 -08:00 committed by GitHub
parent b3c362a454
commit 5dead96c3d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
release-notes/6.0/known-issues.md
View File

@ -31,10 +31,6 @@ To fix this, edit your `PATH` environment variable to either remove the `c:\Prog
## ASP.NET Core
### Running Blazor WebAssembly using IIS Express in Development
As of .NET 6 Preview 1, there is an ongoing issue with running Blazor WebAssembly applications using an IIS Express server during development on Visual Studio. As a workaround, we recommend using Kestrel during development.
### SPA template issues with Individual authentication when running in development
The first time SPA apps are run, the authority for the spa proxy might be incorrectly cached which results in the JWT bearer being rejected due to Invalid issuer. The workaround is to just restart the SPA app and the issue will be resolved. If restarting doesn't resolve the problem, another workaround is to specify the authority for your app in Program.cs: `builder.Services.Configure<JwtBearerOptions>("IdentityServerJwtBearer", o => o.Authority = "https://localhost:44416");` where 44416 is the port for the spa proxy.