Merge pull request #453 from DuendeSoftware/anders/wilson-version

Add note on Microsoft.IdentityModel package versions to upgrade guide

IdentityServer/v7/docs/content/upgrades/v6.3_to_v7.0.md

@@ -140,9 +140,8 @@ Some organizations prefer to use other tools for managing schema changes. You're
 
 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.
+## Step 6 (if needed): 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 like `Microsoft.Data.SqlClient.SqlException (0x80131904): The syntax near '$' is incorrect.` or `Microsoft.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near the keyword 'WITH'.` Please see https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-8.0/breaking-changes#mitigations for more information.
-- For container deployments, the [default ASP.NET Core port changed from 80 to 8080](https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/8.0/aspnet-port). This might require configuration updates to either continue using port 80 or to migrate to using 8080.
+- For container deployments, the [default ASP.NET Core port changed from 80 to 8080](https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/8.0/aspnet-port). This might require configuration updates to either continue using port 80 or to migrate to using 8080.
+ - IdentityServer and the Asp.Net Authentication packages all depends on the `Microsoft.IdentityModel.*` packages. With packages that are brought in as transient dependencies there is less control of the versions being pulled in. If different packages from the `Microsoft.IdentityModel.*` family end up having different versions, there will be odd bugs. We've seen reports where the refresh token isn't stored and where the OIDC handler fails to redirect to an OIDC Provider because it failed reading the discovyer document. **Always ensure that all Microsoft.IdentityModel.\* packages are of exactly the same version**. If they are not, you might need to make an explicit `<PackageReference>` to pin an exact version.