Activities of "balessi75"

Hi @liangshiwei,

Thanks for verifying, the login issue had to do with something on our end that we corrected.

But we were hoping to get more information about the link sent to emails such as the 'Forgot Password' link.

We tried... "SelfUrl": "https://{{tenantName}}.localhost:44327",

...but that didn't work. How and were does the {{tenantName}} placeholder get put into the SelfUrl? Is there another step? Also, we extended the tenant entity to have a "host" column for subdomain resolution. We tried replacing {{tenantName}} with {{host}} but that didn't work either.

When I go to tenant1.domain.net, I can see while debugging, that the custom tenant resolver finds the proper tenant based on the 'tenant1' sub domain.

The problem is that when I go to sign in, I'm properly authenticated against the tenant 'tenant1', but when the following occurs at the end of the login process...

return Redirect(GetRedirectUrl(returnUrl, returnUrlHash));

...I'm sent back to the domain.net instead of tenant1.domain.net which is the URL I originally accessed to login. This causes the login screen to show up again after properly authenticating against tenant1.domain.net.

The 'returnUrl' parameter comes from Volo.Abp.Account.Public.Web.Pages.Account.AccountPageModel.

Also, when a 'forgot password' email is sent with a confirmation link, the link generated always points back to the domain.net URL instead of the tenant1.domain.net URL that was used when clicking the 'Forgot Password' link.

Thanks @liangshiwei ! That was exactly the problem.

I have another question though relating to this were we are creating a custom tenant resolver that resolves based on subdomain.

Using https://blog.antosubash.com/posts/abp-extend-tenant-with-custom-host We now have the tenant properly being resolved based on subdomain, but every redirect goes back to the main domain without the tenant's current subdomain in the URL.

I'm assuming the redirect information is coming from appsettings.json's "App:SelfUrl" and/or "App:RedirectAllowedUrls" settings. How can the system be aware of the tenant subdomain in the URL when the system is redirecting or a user clicks on a email confirmation link? Any information and/or examples you can share would be greatly appreciated.

Thanks

ABP 7.0.1 Commercial / Blazor Server / EF / Separated IDS / Non-tiered

Hi,

We are following the exact steps in the following blog post: https://blog.antosubash.com/posts/abp-extend-tenant-with-custom-host

The CustomTenantRepository in the example has the following method:

 public async Task<Tenant> GetTenantByHost(string host, CancellationToken cancellationToken = default)
    {
        var context = await GetDbContextAsync();
        var tenant =  context.Tenants.Where(u => EF.Property<string>(u, "Host") == host);
        return await tenant.FirstOrDefaultAsync(cancellationToken: cancellationToken);
    }

The problem we are having is that the context.Tenants.Where method appears to be querying the table AbpTenants instead of SaasTenants. The following SQL Server exception occurs: Invalid object name 'AbpTenants'.

Please advise. Thank you in advance.

Hi @liangshiwei,

AddAppSettingsSecretsJson() is not a method of IConfigurationBuilder, so the change to DbContextFactory didn't work for us.

FYI - Instead, we got it to work by adding the following to the CreateHostBuilder method of Program.cs in the DbMigrator project.

  .ConfigureAppConfiguration((hostContext, builder) =>
            {
                if (hostContext.HostingEnvironment.IsDevelopment())
                {
                    builder.AddUserSecrets<Program>();
                }
            })
           

ABP 7.0.1 Commercial / Blazor Server / EF / Separated Tenant and Host DBs / Non-tiered

Hi,

In order for developers to use local DBs without their local DB references being checked into source control, we attempted to use .NET's 'Manage User Secrets' feature for the DBMigrator project (secrets.json).

We are finding though that the framework still uses the connection string under the standard appsettings.json file for the DBMigrator project. When using the secrets.json feature under the Blazor project, everything works as expected. Is this by design or is there something we are missing with regards to the DBMigrator project?

Thanks in advance,

-Brian

Thanks @liangshiwei, this worked perfectly

Excellent, thanks @liangshiwei

ABP Commercial 7.0.1 / EF / Blazor Server / Separate Host and Tenant DBs / Non-tiered

Hi,

While testing our upgrade from 5.2.0 to 7.0.1, we found that on the 'My Account' -> 'Personal Info' area, when a phone number is changed and then saved, the 'Verify' button no longer appears and the user is no longer prompted to verify their phone number.

We confirmed the issue with a newly templated project, and found that in...

Volo.Account.Pro\src\Volo.Abp.Account.Pro.Public.Web\Pages\Account\Components\ProfileManagementGroup\PersonalInfo\Default.js

..the following 'false' parameter is now being passed to .serializeFormToObject in v7.0.1

var input = $("#PersonalSettingsForm").serializeFormToObject(false);

This is what seems to be causing the issue as we overrode Default.js and removed the false parameter (as it was in v5.2.0) and the problem is resolved.

Please advise if this is the correct workaround and if this will be fixed in the next version.

Thanks

Thanks, @liangshiwei! This was everything I needed to customize the personal settings area as needed.