Activities of "maliming"

hi

But when we call verify password reset token with 6 digit code it validates all the time except when a new one created.

What is your code?

Thanks.

hi

You can

1. Change the IdentitySessionConsts.MaxDeviceInfoLength and add a new EF Core migration to increase the length of the session entity.

public class IdentitySessionConsts
{
    public static int MaxSessionIdLength { get; set; } = 128;

    public static int MaxDeviceLength { get; set; } = 64;

    public static int MaxDeviceInfoLength { get; set; } = 64;

    public static int MaxClientIdLength { get; set; } = 64;

    public static int MaxIpAddressesLength { get; set; } = 2048;
}

2. Replace the built-in IWebClientInfoProvider service.

using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Logging;
using MyCSharp.HttpUserAgentParser.Providers;
using Volo.Abp.DependencyInjection;

namespace Volo.Abp.AspNetCore.WebClientInfo;

[Dependency(ReplaceServices = true)]
[ExposeServices(typeof(HttpContextWebClientInfoProvider), typeof(IWebClientInfoProvider))]
public class MyHttpContextWebClientInfoProvider : HttpContextWebClientInfoProvider
{
    public MyHttpContextWebClientInfoProvider(
        ILogger<HttpContextWebClientInfoProvider> logger,
        IHttpContextAccessor httpContextAccessor,
        IHttpUserAgentParserProvider httpUserAgentParser)
        : base(logger, httpContextAccessor, httpUserAgentParser)
    {
    }

    protected override string? GetDeviceInfo()
    {
        var info = base.GetDeviceInfo();
        return info?.Substring(0, 64);
    }
}

hi

I will add an internal issue to track this.

Thanks.

hi

Checking it in OpenIdConnectEvents methods is a good approach.

Thanks.

hi

SupportTwoFactor: Whether the user has an available two-factor authentication method, such as email confirmation, phone number verification, or an authenticator app.

TwoFactorEnabled: Whether the user has enabled two-factor authentication.

Thanks

hi

I will check this. Thanks.

hi

You can check this https://abp.io/support/questions/9777/AccountLogout-400-response-code---After-upgrading-from-822-to-911#answer-3a1bd776-69af-aee5-4dd0-b040e3923d16

Thanks.

Thank you for your solution. 👍

hi

What error/exception did you get now?

Thanks.

hi

We need the entity tracking feature when we update an entity. see https://learn.microsoft.com/en-us/ef/core/change-tracking/

You can try to disable it in MyEfCoreIdentityUserRepository.cs‎ when querying entities.

The solution is:

So you can either prevent assigning too many organzation to a user or modify the Identity module code to avoid loading all navigation entities explicitly. Then, query all entities at once as needed and tell EF Core not to track them.

https://abp.io/docs/latest/framework/architecture/domain-driven-design/repositories#read-only-repositories https://abp.io/docs/latest/framework/architecture/domain-driven-design/repositories#read-only-repositories-behavior-in-entity-framework-core