[Identity] SetLockoutEndDateAsync can't set a time before existed value

[ngyyuusora]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

await _adminUserManager.SetLockoutEndDateAsync(user, new DateTimeOffset(2999, 1, 1, 0, 0, 0, TimeSpan.Zero));

then set same user

await _adminUserManager.SetLockoutEndDateAsync(user, new DateTimeOffset(2030, 1, 1, 0, 0, 0, TimeSpan.Zero));
Console.WriteLine(await _adminUserManager.GetLockoutEndDateAsync(user));

still 2999 (also in DB)

Expected Behavior

LockoutEnd value should be updated.

Steps To Reproduce

netcore9.0 with mysql

Exceptions (if any)

No response

.NET Version

9.0.104

Anything else?

user.LockoutEnd = DateTimeOffset.UtcNow;
_manager.UpdateAsync(user);

works

[ngyyuusora]

Sorry, it's a design behavior

  if (!await store.GetLockoutEnabledAsync(user, CancellationToken).ConfigureAwait(false))
        {
            Logger.LogDebug(LoggerEventIds.LockoutFailed, "Lockout for user failed because lockout is not enabled for this user.");
            return IdentityResult.Failed(ErrorDescriber.UserLockoutNotEnabled());
        }
        await store.SetLockoutEndDateAsync(user, lockoutEnd, CancellationToken).ConfigureAwait(false);
        return await UpdateUserAsync(user).ConfigureAwait(false);