ConfigureApplicationCookie does not work with AddDefaultIdentity

[wutever0]

Using ConfigureApplicationCookie to change the LoginPath only works with AddIdentity but not with AddDefaultIdentity, even after adding the configuration after AddDefaultIdentity as per #1414 .

            services.AddDefaultIdentity<IdentityUser>(); //Redirects to Account/Login
            //services.AddIdentity<IdentityUser, IdentityRole>(); //Redirects to Account/LoginRegister

            services.Configure<IdentityOptions>(options =>
            {
                // Password settings.
                options.Password.RequireDigit = false;
                options.Password.RequireLowercase = false;
                
                .....

                // User settings.
                options.User.AllowedUserNameCharacters =
                "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-._@+";
                options.User.RequireUniqueEmail = false;
            });

            services.ConfigureApplicationCookie(options =>
            {
                options.LoginPath = $"/Identity/Account/LoginRegister";
            });

[wutever0]

This seems to be specifically an issue with AddDefaultUI (which is also called in AddDefaultIdentity).
When I use the following:

            services.AddIdentity<IdentityUser, IdentityRole>()
                  .AddDefaultTokenProviders()
                  .AddDefaultUI();

I am again unable to redirect to my custom login page. This is a bit confusing because as far as I understand adding a default UI should not be interfering with cookie settings or am I wrong?

Would welcome any help or suggestions I've spent several days now trying to do this the right way.

Note: IdentityDefaultUIConfigureOptions has a PostConfigure that seems to set this. Is this where things are being messed up?

[AndrewTriesToCode]

I'm noticing this same issue. This breaks certain multi tenant scenarios in my use case.

[blowdart]

@javiercn does this fall under your scaffolding work?

[javiercn]

I think the PostConfigure is the one causing this, you can write services.PostConfigure<CookieAuthenticationOptions>(IdentityDefaults.ApplicationCookie, o => ...) to change the paths.

[blowdart]

@Eilon Who is supporting Identity UI and scaffolding now? No-one seems to want it.

[Eilon]

@mkArtakMSFT is working in the answer to that question.

[javiercn]

Closing this issue as the question has been answered and there's no more action to be taken here. See the answer above.

Thanks!

[AndrewTriesToCode]

@javiercn

Just to be clear, when you say "there will be no action to fix this" do you mean no change will be made or that it is slated for 3.0?

[javiercn]

From what I understand yes. Adding @HaoK who made the suggestion to make this postconfigure in the first place to see if he wants to reconsider.

[HaoK]

Seems simple enough to just move the cookie options settings into the normal configure.