You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Breaking change in SignInManager constructor (new parameter)
As part of adding support for new email/confirmation flows in Identity(dotnet/aspnetcore#8356), we added a new IUserConfirmation<TUser> argument to the constructor of SignInManager
Version introduced
3.0
Old behavior
SignInManager didn't require IUserConfirmation when constructing.
New behavior
SignInManager requires an IUserConfirmation.
Reason for change
Adding support for new email/confirmation flows
Recommended action
If manually constructing a SignInManager pass in an implementation of IUserConfirmation or grab one from DI to pass in.
Just wanted to drop comment in here for others, as this was a little confusing for me.
The Microsoft.NET.Sdk.Web SDK has AspNetCore.Identity package included now, but Nuget only has the package up to version 2.2. Visual Studio tries to automatically install that version (2.2) from Nuget if your library project targets the regular SDK (Microsoft.NET.Sdk). This has incompatibilities if you are then referencing that library project from for example a WebApi project.
The solution is to remove all Nuget dependencies in your library projects, open up the .csproj file, and change the SDK
<ProjectSdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<OutputType>Library</OutputType>
</PropertyGroup>
<!-- other configs -->
</Project>
Breaking change in SignInManager constructor (new parameter)
As part of adding support for new email/confirmation flows in Identity(dotnet/aspnetcore#8356), we added a new
IUserConfirmation<TUser>
argument to the constructor ofSignInManager
Version introduced
3.0
Old behavior
SignInManager
didn't requireIUserConfirmation
when constructing.New behavior
SignInManager
requires anIUserConfirmation
.Reason for change
Adding support for new email/confirmation flows
Recommended action
If manually constructing a
SignInManager
pass in an implementation ofIUserConfirmation
or grab one from DI to pass in.Category
ASP.NET Core
Affected APIs
SignInManager.ctor
Issue metadata
The text was updated successfully, but these errors were encountered: