Follow up your suggestion, it still cannot resolve the issue, your approach will lose the tenant, it will cause current tenant user cannot login.
I think this is a bug, remove "http://" or "https://" already implemented in [https://github.com/aspnetboilerplate/aspnetboilerplate/blob/dev/src/Abp.AspNetCore/AspNetCore/MultiTenancy/DomainTenantResolveContributer.cs])
@ ismcagdas , What do you think?
Is there a way that could define the localization string for enumerable variants? Such as below enumerable class:
/// <summary>
/// Represents an evaluated result item status enumeration
/// </summary>
public enum FeedbackStatus
{
/// <summary>
/// Active
/// </summary>
Active = 10,
/// <summary>
/// Resolved
/// </summary>
Resolved = 20,
/// <summary>
/// Won't fix
/// </summary>
WillNotFix = 30,
/// <summary>
/// Closed
/// </summary>
Closed = 40
}
Then they will be used as a dropdownlist, but how to get the localization string when it is rendering.
Look forward to this feature, an urgent requirement based on Token authentication mechanism.
Yes, the behavior just like you said, on the UI the process is that.
But, when I using tenant1.mydomain.com visit the site, in fact the application doesn't found the tenant, if using the user of the tenant sign in system then will failed.
This is the issue that I encountered now.
Version 1.4.2
As we know in aspnet core version, the WebSiteRootAddress already move to appsettings.json, if change the WebSiteRootAddress like {TENANCY_NAME}.mydomain.com, use subdomain visit the site, it cannot find the tenant, furthermore on the login page, the change tenant name link disappeared.
If change the WebSiteRootAddress as <a class="postlink" href="http://www.mydomain.com">www.mydomain.com</a>, use subdomain visit the site, although it cannot find the tenant, but on the login page, the change tenant name link can update the tenant name, then login could redirect to tenant admin panel.
Is the feature still works fine? It is difficult to find a specificed tenant by subdomain with this bug.
Any suggestion?
<cite>Alex: </cite> I also have the exact same issue. I would like to use a more granular general return value than userfriendlyException. You might look at AjaxResponse object in ABP framework. I think that is what you mean. But I don't know what would be the side effect of using it in xAppService classes. Because ABP and Zero, do many things automatically.
Yes, I had considered try to use AjaxResponse, but it is complex to extend it, it will impact ABP original more.
I found the reason, it caused by I applied a workaround fix for [https://github.com/aspnetboilerplate/aspnetboilerplate/issues/1836]).
After upgraded to v1.4.2 and also applied this workaround in Web.Core project in aspnet zero, it caused the ImpersonateSignIn failed, it confused me a lot of time.
If only upgrade to v1.4.2, doesn't invoke the Resolvers.Clear(), it works fine.
No special steps to reproduce,just like normally long on as the host,then choose a tenant to impersonate the user singin,in ImpersonateSignIn action of Account controller will throw the exception,it seems AbpSession.TenantId is null cuased this issue .
Anybody encountered this issue too?