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

Merge pull request #6791 from dotnet/haok/notes

Browse source 
Add spa + auth known issues
This commit is contained in:
Rahul Bhandari 2021-10-12 08:43:16 -07:00 committed by GitHub
parent 5add597965 40f3c0a0b9
commit bb64413165
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
release-notes/6.0/known-issues.md
View file

@ -166,3 +166,9 @@ You can workaround this by always providing a non-zero and non-minimum value for
When enabling HTTP/3 which is only accessible through a feature flag, you might experience Kestrel using 100% of the CPU. We recommend not enabling the feature until this is fixed.
Issue is tracked by https://github.com/dotnet/runtime/issues/60133 and will be fixed in .NET 6 RTM.
**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.
When using localdb (default when creating projects in VS), the normal database apply migrations error page will not be displayed correctly due to the spa proxy. This will result in errors when going to the fetch data page. Apply the migrations via 'dotnet ef database update' to create the database.