Pavel Voronin

@Bernoulli-IT, well, I have this issue even for Bearer auth in ASP.NET Core 3 ```CSharp services .AddAuthentication(JwtBearerDefaults.AuthenticationScheme) .AddJwtBearer(opt => { opt.TokenValidationParameters = new TokenValidationParameters { ClockSkew = TimeSpan.FromMinutes(5), RequireSignedTokens =...

Are you making any changes to docker images? ``` PS > docker pull mcr.microsoft.com/dotnet/sdk:8.0 8.0: Pulling from dotnet/sdk fd674058ff8f: Already exists bbdcc09b9436: Already exists 22a0038f868f: Already exists 4416e5d0ee0a: Already exists...

+1 for the feature.

I've recently filed an issue to EF Core: If same migrations history table is reused between different db contexts (default behavior) then `List Applied Migrations` shows all migrations and not...

You are [mean](https://github.com/dotnet/aspnetcore/blob/febd7e8bdf05f17fb4e0e4dd3123e9538fbf7e7b/src/Http/Authentication.Core/src/AuthenticationCoreServiceCollectionExtensions.cs#L24C9-L24C140), gentlemen =) Tried to decorate it with Scrutor, but did not expect it's registered as a singleton.

[The fact that it is not composed](https://github.com/dotnet/aspnetcore/issues/46120) deserves a special NOTE.

Ok, thanks, @AndriySvyryd. So `add navigation` from the error message means calling `Has|OwnsOne|Many`. Not that obvious TBH, because it's all about configuring mappings. Maybe you could slightly change the wording...

@AndriySvyryd , by the way, I see that order: `Navigation()` and `HasMany()` does not cause an issue. Looks like it matters only for owned entities.

@AndriySvyryd Will public property of any type implementing `IEnumerable` be treated as navigation?

@vdanche , how did you install 9.0.100-rc.2.24467.36 ?