UseRequestLocalization() call has to be placed after UseAuthentication()

[joakimriedel]

I've tried to migrate a net core 2.2 web application to net core 3.0 preview 9. I'm having troubles with middleware, where HttpContext.User.Identity.IsAuthenticated always returns false even if the user is authenticated. To ensure that I do not made any mistakes during migration of our application, I even tried to set up a new 3.0 web application project and follow the instructions on this page. In the code below IsAuthenticated is always false.

How do I make this work in 3.0? I have to check authenticated user to resolve the culture based on a SQL query.

                options.RequestCultureProviders.Insert(0, new CustomRequestCultureProvider(async context =>
                {
                    var isAuthenticated = context.User.Identity.IsAuthenticated; // always false in 3.0 preview9
                    // My custom request culture logic
                    return new ProviderCultureResult("en");
                }));

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
• Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
• Content: Globalization and localization in ASP.NET Core
• Content Source: aspnetcore/fundamentals/localization.md
• Product: aspnet-core
• Technology: aspnetcore-fundamentals
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

@ryanbrandenburg please review.

[Rick-Anderson]

@jcemoller ping me if you don't get a response by end of day 9-11.

[joakimriedel]

@Rick-Anderson spent the last two days trying to find any resolution to this, and I think I found one. It seems that in 3.0, the UseRequestLocalization() call has to be placed after UseAuthentication() call in Configure(). Previously, in 2.2 and also as noted in the documentation under https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization?view=aspnetcore-3.0#implement-a-strategy-to-select-the-languageculture-for-each-request, the recommendation was to place UseRequestLocalization() before UseStaticFiles() and UseAuthentication().

I have yet to find any side-effects by moving the call later in setup, but if this is the new policy it should be reflected in the docs for 3.0. Thanks.

[Rick-Anderson]

@ryanbrandenburg please review.

[joakimriedel]

@Rick-Anderson any news now for rtm?

[Rick-Anderson]

@mkArtakMSFT please assign a reviewer.
@ryanbrandenburg can you review - this looks short but important.

[ryanbrandenburg]

This issue was moved to dotnet/aspnetcore#14391

[ryanbrandenburg]

Seems like this is a technical problem/question rather than a docs question. I've moved it to aspnet/AspNetCore where we track that kind of thing.