Activities of "balessi75"

Abp Commercial 5.2.0 / Blazor Server / EF Core / Non-tiered

Hi,

We have extended the IdentityUser entity with a new property but need to have the property only visible on the user listing (needs to be hidden on the create and edit modal). To accomplish this, we implemented the following in our ProjectNameModuleExtensionConfigurator class:

   user.AddOrUpdateProperty<string>( 
                        EmployeeConsts.FullName 
                       , property =>
                       {
                            property.DisplayName = LocalizableString.Create<TimepieceResource>(
                               "DisplayName:FullName");
                           property.DefaultValue = null;
                           property.UI.OnCreateForm.IsVisible = false;
                           property.UI.OnEditForm.IsVisible = false;
                           property.UI.OnTable.IsVisible = true;
                        }
                    );

The extended property, however, is still visible on the create and edit modals.

Are we doing something wrong, or is this a bug?

Thanks in advance.

Hi,

Abp Commercial 5.2.0 / Blazor Server / EF / Non tiered

1. We noticed that, unlike the EasyCRM demo, none of the grids from the dependent modules (user, roles, etc.) have sorting or user settable page size capabilities.
2. There is some inconsistency to item 1, only Boolean columns seem to be sortable, however, the sort does not work when clicking the column header. All other column types (string, int, etc.) are not sortable
3. We extended the IdentityUser entity with a custom column and the custom columns do appear to be sortable in the user management page, but like 2 above, the sort does not work
4. Since the sort on our extended column is not working, we decided to override the SetTableColumnsAsync method of the user management page and set the extended column's 'Sortable' property to false, but the column is still sortable at runtime.

Please let us know if these are things that will be looked at and if there are workarounds or suggestions.

Thanks in advance, Brian

Ok, thanks for confirming.

Abp Commercial 5.1.3 / Blazor Server / EF / Non-Tiered

Hi, We have a requirement as a host admin to be able to impersonate any user on any tenant and have run into a problem when testing this scenario.

• As a host admin, we can successfully impersonate any tenant
• Once we impersonate a tenant, we are always logged into that tenant as it's Admin user
• Now we want to impersonate a standard user in that tenant, but when we do so, the option to impersonate a user is not available even though the tenant Admin has impersonate permissions.
• If we login directly to the tenant as an admin without being impersonated from the host, then the impersonate user option is available.

Are we going about this correctly? Guidance is appreciated as always.

I was using the wrong localization key.

Instead of: "Feature:TwoFactor": "Two Factor"

I needed: "DisplayName:Abp.Identity.TwoFactorBehaviour": "Two Factor"

Ok, that makes sense for two factor, but what we are actually testing here is the 'Require Verified Phone' option, which requires a verified Phone to sign in. Once verified, the user can sign in - this applies even if two factor is turned off.

When this setting is turned on, Abp allows the user to verify their phone during the sign in process. So what we are finding is that during the verification process, they get one chance to enter their phone, from there, if they entered the wrong phone, it's saved to the database and can never be updated again. Therefore, the user can never login.

I've updated the issue title to more accurately reflect the issue.

Abp Commercial 1.5.3 / Blazor Server / EF / Non-Tiered

Hi, We noticed that when phone verification is required to sign in, the first attempt to save the phone number at login is saved to the database before the phone number is verified. If the number is never verified, say because they typed the wrong number in, the number input recalls the previous value from the database and is then always disabled on the login UI - so the user can never correct the number to be verified.

Is this by design? And if so, I'm just curious about the rational...

Thanks in advance!

hi

https://community.abp.io/posts/how-to-override-localization-strings-of-depending-modules-ba1oy03l https://github.com/abpframework/abp-samples/tree/master/DocumentationSamples/ExtendLocalizationResource

Hi @maliming,

We've followed the community article and still can't seem to find were we are going wrong.

For the Feature:TwoFactor localization, should we be adding the virtualized json file from the Domain.Shared project's ConfigureServices method? Also, is it correct to be using the IdentityResource when adding the localized json file?

Application project reference to the DbMigrator project and I am still getting the same exception

Did you add the module dependency?

[DependsOn( 
    ..... 
    typeof(...ApplicationModule) 
    )] 
public class ...DbMigratorModule : AbpModule 

That was it! Thanks for the support @liangshiwei

Abp Commercial 5.1.3 / Blazor Server / EF

Hi, We've added the following to the ConfigureServices method of our Domain.Shared project:

Within the Domain.Shared/Localization/Extensions we have our en.json file set as an embedded resource. In the localization file we are attempting to override the Feature:TwoFactor localization value from the Identity Module. At runtime, however, we don't see the modified label.

We also tried putting the above code in the ConfigureServices method of our Application.Contracts project.

Any guidance is greatly appreciated.