Activities of "balessi75"

Ok, thanks for confirming.

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.

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

Hi,

Setting definitions in the ..Account.Application project. you can add the Application project reference to the DbMigrator project.

Hi Liangshiwei,

I added our ...Application project reference to the DbMigrator project and I am still getting the same exception. The DataSeedContributer is in the Domain project. It needs to be there, correct? I tried adding a DataSeedContributer to the Application project, but DbMigrator does not discover the DataSeedContributer at runtime from that location.

We have a TemplateDefinitionProvider defined in our Domain project

hi

Can you try moving it into your Application.Contracts module?

Thank you maliming, that resolved the issue!

It seems there is a styling issue on the Lepton Theme. I've added it to our backlog and We'll do it asap.

Excellent, thank you @enisn

It appears that the IValidatableObject validation doesn't wrap the error "Last Name is Required" in a <span> . After looking at the Lepton css in chrome's dev tools, I found that once I wrapped the error text in a span element using Chrome, the styling was corrected.

Any workaround that can be suggested or is this a possible fix at some point?

hi

For 6-digit codes it is valid for 3 minutes, others default to 1 day, of course you can configure it. This belongs to ASP NET Core Identity.

https://github.com/dotnet/aspnetcore/blob/main/src/Identity/Extensions.Core/src/Rfc6238AuthenticationService.cs#L16

https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.identity.dataprotectiontokenprovideroptions.tokenlifespan?view=aspnetcore-6.0#microsoft-aspnetcore-identity-dataprotectiontokenprovideroptions-tokenlifespan

Excellent! Thank you @maliming!