I'm not support.. but...
FWIW - the namespace you pick will propogate into the UI, and you'd have to go and find and replace it.
I made the same mistake, which sucks, as there's not really an easy way.
My suggestion would be to generate your app using a namespace that is very unique - so it's very easy to find in your project.
For example, let's say your app is going to be something common, like the word Filter.
Finding and replacing that would be a nightmare
So I'd suggest you make it something like FilterApp. Then, you can search your project for FilterApp.
It will, of course, come up with all the namespace rows, but you can go through your find in VS and quickly change them.
The name will be sprinkled everywhere. Email templates, work.xml.. etc..
I'm facing the same issue and considered regenerating my project to get a new name, but frankly it's just not worth the effort of moving the code over if you are down the road.
So again, my suggestion is to pick something that you wouldn't normally see in code (c3, css, html, or otherwise). The more unique in the universe, the easier your job will be.
AppFilterBackendNS, or BackendNSFilterApp, or even go with something crazy like AAABBBCCCDDDD, that will make it exceptionally easy to find.
At the end of the day, if you think you're going to need to change your namespace, your release is keyed to your namespace.
If you've already downloaded one, you can do one more. If you haven't, then I strongly recommend using something that would be ok in release or dev, and that follows the guidelines I suggested.
If you're concerned about how your namespace will appear externally, then I'd do something very descriptive. Lets say you work for ATI.. then make something ATIFilterAppNameSpace.
Yeah, a lot to type, but in reality I've not found myself typing my namespace a lot; but that will depend on where you drop your classes and what namespace you put them in.
HTH
This is related to https://support.aspnetzero.com/QA/Questions/9441/Cannot-Complete-Authentication-After-Chrome-Windows-Update--Local-State-File-Data-Conflict-in-Windows-User-App-Data
This is 8.9, JQ
The issue is with Chrome 84.0.4147.105 in my case, multiple users.
No modifications to any of the authentication code and everything works great, except for some users that use this version of Chrome. Testing in production, we created a new Tenant, and he is unable to login.
I've been able to recreate this in development environment by adding my domain, and his tenant name + my domain to my hosts file, modifying IIS express configuration to listen on port 80, and pointing my dev environment at the production database. Lastly, I took the Local State file for the user and copied that to my Chrome profile.
User logs in - it posts and redirects to /App
Which immediately redirects back to login.
In the IIS logs:
INFO 2020-07-31 22:26:26,118 [10 ] Microsoft.AspNetCore.Hosting.Diagnostics - Request starting HTTP/1.1 GET http://{Tenant}.{My Domain}/App
INFO 2020-07-31 22:26:26,127 [10 ] uthorization.DefaultAuthorizationService - Authorization failed.
INFO 2020-07-31 22:26:26,129 [10 ] tion.Cookies.CookieAuthenticationHandler - AuthenticationScheme: Identity.Application was challenged.
In my instance, no users for my new tenant are able to login with Chrome if they've logged in before it was updated,
The only resolution it have them remove the Local State file from the browser profile folder in app data.
I have my site deployed to Azure (linux) and am not using SSL at the moment, we're not live yet.
BTW - in looking at ABP code - I'm wondering if this is related:
Also, on my end, no user can login to my tenant, regardless of profile.
We're going to need someone from support to resolve this - It authenticates, redirects to app - and somewhere inside ABP or the ANZ modules, the following tems get logged and it redirects from App back to login.
INFO 2020-07-31 18:35:18,271 [24 ] uthorization.DefaultAuthorizationService - Authorization failed.
INFO 2020-07-31 18:35:18,271 [24 ] tion.Cookies.CookieAuthenticationHandler - AuthenticationScheme: Identity.Application was challenged.
So I was finally able to get this running in debug.
had to modify IIS Express config, hosts file, etc.
But this failure is happening somewhere deep; maybe in something closed source?
So here's what I've found in my logs:
result.Succeeded, sending Microsoft.AspNetCore.Mvc.JsonResult
Executing JsonResult, writing value of type 'Abp.Web.Models.AjaxResponse'.
Executed action XXXXXX.Web.Controllers.AccountController.VerifySecurityCode (XXXXXX.Web.Mvc) in 378.4956ms
Executed endpoint 'XXXXXX.Web.Controllers.AccountController.VerifySecurityCode (XXXXXX.Web.Mvc)'
Request finished in 414.1965ms 200 application/json; charset=utf-8
Request starting HTTP/1.1 GET http://YYYYYYYYYYYYYYY/App
Authorization failed.
AuthenticationScheme: Identity.Application was challenged.
Request finished in 12.6433ms 302
Request starting HTTP/1.1 GET http://YYYYYYYYYYYYYYY/Account/Login?ReturnUrl=%2FApp
Authorization Failed on the App request
By the way - my server does NOT have SSL enabled right now - so it's pure http and I'm having same problem.
I finally was able to recreate against my azure production server (with no SSL currently installed) by using an affected Local State file.
I'll update here if I learn anything.
Is this your dev environment? If so - do you know a way to recreate the issue on a machine that doesn't have the problem? I tried taking a Local State file from a user's machine that had the issue but it didn't work. Perhaps it's my profile. I'll try using the local state file and hitting my production and trying to login as an affected user.
I can't recreate in dev, so I'm feeling around in the dark here.
However, I really wish someone from support would offer some suggestions.
Have you opened a ticket on gitHub yet?