Difference between AspNetUsermanager and UserManager

user_1525840 0
Viewed 193

NB I got warning that there are many similar questions available. However, those are mostly regarding other concepts such as difference between user managers and user stores (and also, difference between a bunch of unrelated things, so I'm guessing Stacky weights in difference equally). However, googling difference AspNetUserManager UserManager produces a lot of guides on how to set up security without discussing the actual difference.

So, I went to the good old MSDN and looked up those two classes. Apparently, AspNetUsermanager is described like this.

Provides the APIs for managing user in a persistence store.

And that, while UserManager is described like this.

Provides the APIs for managing user in a persistence store.

One would expect certain overlap in functionality between those two, given that both are meant for managing users. However, I feel that it might behoove the reader to be presented with a bit more variation in the, certainly so, true formulation.

My question is - how do they relate (i.e. under what circumstances is the former preferred over the latter)?

asp.net-core user-management identity c#
1 Answers

If I check the code, the only difference is that AspNetUserManager<TUser> gets the (default) cancelationtoken from the httpcontext (on request aborted). I guess that gives a better experience when canceling the request. All other methods and properties are inherited from the UserManager<TUser>

/// <summary>
    /// Provides the APIs for managing user in a persistence store.
    /// </summary>
    /// <typeparam name="TUser">The type encapsulating a user.</typeparam>
    public class AspNetUserManager<TUser> : UserManager<TUser>, IDisposable where TUser : class
    {
        private readonly CancellationToken _cancel;

        /// <summary>
        /// Constructs a new instance of <see cref="AspNetUserManager{TUser}"/>.
        /// </summary>
        /// <param name="store">The persistence store the manager will operate over.</param>
        /// <param name="optionsAccessor">The accessor used to access the <see cref="IdentityOptions"/>.</param>
        /// <param name="passwordHasher">The password hashing implementation to use when saving passwords.</param>
        /// <param name="userValidators">A collection of <see cref="IUserValidator{TUser}"/> to validate users against.</param>
        /// <param name="passwordValidators">A collection of <see cref="IPasswordValidator{TUser}"/> to validate passwords against.</param>
        /// <param name="keyNormalizer">The <see cref="ILookupNormalizer"/> to use when generating index keys for users.</param>
        /// <param name="errors">The <see cref="IdentityErrorDescriber"/> used to provider error messages.</param>
        /// <param name="services">The <see cref="IServiceProvider"/> used to resolve services.</param>
        /// <param name="logger">The logger used to log messages, warnings and errors.</param>
        public AspNetUserManager(IUserStore<TUser> store,
            IOptions<IdentityOptions> optionsAccessor,
            IPasswordHasher<TUser> passwordHasher,
            IEnumerable<IUserValidator<TUser>> userValidators,
            IEnumerable<IPasswordValidator<TUser>> passwordValidators,
            ILookupNormalizer keyNormalizer,
            IdentityErrorDescriber errors,
            IServiceProvider services,
            ILogger<UserManager<TUser>> logger)
            : base(store, optionsAccessor, passwordHasher, userValidators, passwordValidators, keyNormalizer, errors, services, logger)
        {
            _cancel = services?.GetService<IHttpContextAccessor>()?.HttpContext?.RequestAborted ?? CancellationToken.None;
        }

        /// <summary>
        /// The cancellation token associated with the current HttpContext.RequestAborted or CancellationToken.None if unavailable.
        /// </summary>
        protected override CancellationToken CancellationToken => _cancel;
   }

From https://github.com/dotnet/aspnetcore/blob/main/src/Identity/Core/src/AspNetUserManager.c

Very related, there is a suggestion to get rid of this class:

Consider adding optional cancellationToken to manager APIs

If we do this in 3.0, we could probably also get rid of the automatic HttpRequest.Aborted hookup, which would let us get rid of the derived AspNetUserManager entirely.

See https://github.com/dotnet/aspnetcore/issues/5763

user_2013030
Related