From 8d63ca68c8b226597b6681103720bdbfdeb5e747 Mon Sep 17 00:00:00 2001 From: Anders Abel Date: Wed, 17 Jan 2024 16:05:25 +0100 Subject: [PATCH] Reference to EF Core 8 breaking changes --- IdentityServer/v7/docs/content/upgrades/v6.3_to_v7.0.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/IdentityServer/v7/docs/content/upgrades/v6.3_to_v7.0.md b/IdentityServer/v7/docs/content/upgrades/v6.3_to_v7.0.md index fd47ffbf..410de845 100644 --- a/IdentityServer/v7/docs/content/upgrades/v6.3_to_v7.0.md +++ b/IdentityServer/v7/docs/content/upgrades/v6.3_to_v7.0.md @@ -140,7 +140,12 @@ Some organizations prefer to use other tools for managing schema changes. You're - The value of the constant *IdentityServerAuthenticationType* has changed from "IdentityServer4" to "Duende.IdentityServer". This constant is used as the value of the authentication type within the [ClaimsIdentity](https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity.-ctor?view=net-7.0#system-security-claims-claimsidentity-ctor(system-security-principal-iidentity-system-collections-generic-ienumerable((system-security-claims-claim))-system-string-system-string-system-string)) that IdentityServer constructs. The authentication type's value is never used by IdentityServer or ASP.NET, so this is unlikely to impact anyone. It is also the name of the default cors policy created by IdentityServer. This could theoretically impact you if you have a CORS policy named "Duende.IdentityServer", as the new name now conflicts. - ## Step 5: Done! That's it. Of course, at this point you can and should test that your IdentityServer is updated and working properly. + +#### Troubleshooting .NET 8 Issues +You are now done with everything related to the IdentityServer upgrade, but we would also like to +add a references to breaking changes in .NET 8 and associated libraries that are likely to +affect the IdentityServer setup. +- Entity Framework Core 8 has some performance improvements in the query generation for Microsoft SQL Server that relies on database features that requires a database compatibility level of at least 130. This can cause errors on database access with `Microsoft.Data.SqlClient.SqlException (0x80131904): The syntax near '$' is incorrect.` Please see https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-8.0/breaking-changes#mitigations for more information. \ No newline at end of file