.NET Authentication .NET 7 Vs .NET 8 in my simple API service

Sebastian Meckovski 0 Reputation points

I’m working on a relatively simple .NET Core web API service that performs CRUD operations on a database. Not sure what's the best way to implement authentication. Here’s the situation:

  1. In .NET 7, I had to manually define all the authentication endpoints.
  2. In .NET 8, these endpoints come predefined out of the box.

My goal is to create a straightforward set of endpoints for the following actions:

  • Login
  • Register
  • Confirm email (including generating a confirmation link and sending it via SMTP)
  • Reset password
  • Social login with Google

However, .NET 8 also includes additional endpoints (like 2FA) that I don’t need for this project. Also, I want to customize the predefined register controller to trigger an SMTP call for sending the confirmation link.


  1. What’s the best approach for achieving my goals?
  2. Should I manually define my own controllers, or can I leverage the .NET 8 predefined ones and selectively disable the ones I don't need? (is that possible)
  3. Can I configure email sending and social login with .NET 8?
  4. Con social login with google be implemented in .NET 8?
  5. Are there any samples that show how to do it?
Microsoft Technologies based on the .NET software framework.
3,331 questions
A set of technologies in the .NET Framework for building web applications and XML web services.
4,130 questions
ASP.NET: A set of technologies in the .NET Framework for building web applications and XML web services.API: A software intermediary that allows two applications to interact with each other.
292 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Bruce (SqlWork.com) 54,626 Reputation points