Improve missing database experience for SPA apps

[SteveSandersonMS]

Repro:

• Install .NET SDK 6.0.100-rtm.21505.64
• Install VS Version 17.0.0 Preview 5.0 [31803.31.main]
• File -> New project, choose ASP.NET Core with React
  • ... with Individual Auth
• Ctrl+F5 to start it running
• In the browser, click Login

Expected:

• Something like a login prompt

Actual:

Based on the console output, this is probably just because the DB hasn't been created yet, but people don't have an easy way to either find that out or know how to fix it.

System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure' to the 'UseSqlServer' call.
       ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot open database "aspnet-MissionLog-53bc9b9d-9d6a-45d4-8429-2a2761773502" requested by the login. The login failed.
      Login failed for user 'username'.
         at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

Update: Yes, running dotnet ef database update fixes it. But still, we should show the UI in the browser that prompts the developer to apply the migrations.

[pranavkm]

Triage: For 6.0, let's document this as known limitation.

For 7.0, we can consider adding some tooling or templating. Alternatively we could consider putting the database creation in the project template.

@adityamandaleeka / @HaoK this is a Identity experience concern, could you look at this?

[HaoK]

@blowdart thoughts?

[blowdart]

Oh how odd. Yea, documentation given this late stage, maybe we fix early in 7 and backport?

[javiercn]

@blowdart @HaoK I think this is something we should actually fix. I remember afterwards that the issue here is caused by Identity Server not using our development key during development and trying to use a key from the database. This was a result of the identity server update to Duende Identity server, so I think we should fix it. Otherwise, customers won't be able to use their own keys in the way we suggest in our docs.

[blowdart]

Ouch, do we know what the fix would look like then? You know this integration better than anyone

[javiercn]

The fix is to figure out what thing to override in DI to populate with our keys

[HaoK]

For context, why do we not just let it use the database to store the key, they would still need a database to login the user right? Isn't a database required eventually anyway for the fetch/login flow to work?

[javiercn]

Yes, but this breaks the experience. You get a react error that you don't know how to interpret instead of the database error page. In addition to that, users updating shouldn't get their app broken or to suddenly start using a different set of keys without them knowing.

[HaoK]

Can you point to the relevant sections in the doc that you are referring to so I can try it out?

[javiercn]

https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity-api-authorization?view=aspnetcore-5.0#example-deploy-to-a-non-azure-web-hosting-provider