As an alternative to setting OnSignIn directly, it should be possible to inherit BasicAuthenticationEvents and override SignInAsync(), register the new events-type in ConfigureSerivces and set it on AuthenticationSchemeOptions.EventsType. The security infrastructure will inject it to AuthenticationHandler.Events when the sheme's AuthenticationHandler is resolved by dependency injection (see here).

However, BasicAuthenticationHandler short-circuits this functionality by calling Options.Events.SignInAsync(context). It should be just Events.SignInAsync(context)

Hi Team,

We recently started migrating our web app from core 2.1 to 3.1, but running into below error.

We know the last and latest version of Microsoft.AspNetCore.Mvc.DataAnnotations is 2.2.0

but after migrating our app from 2.1 to 3.1, we resolved all the issues, but below issue is coming all the time...

i tried all the options... nothing working out... pls help us here and resolve this. We been trying to fix this quite long time.

Could not load type 'Microsoft.AspNetCore.Mvc.DataAnnotations.Internal.NumericClientModelValidatorProvider' from assembly 'Microsoft.AspNetCore.Mvc.DataAnnotations, Version=3.1.32.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

In .NET Core 3.1 this gives an error:

  An unhandled exception has occurred while executing the request.

System.ArgumentNullException: Value cannot be null. (Parameter 'ticket')
at Microsoft.AspNetCore.Authentication.AuthenticateResult.Success(AuthenticationTicket ticket)
at Moon.AspNetCore.Authentication.MSOFBA.MSOFBAuthenticationHandler.HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1.AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(HttpContext context, String scheme)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

the ticket cannot be null...