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

Question

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.

Questions:

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?

Answer 1

Just like .net 7, you can scaffold identify and make what ever modifications you like:

https://learn.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-8.0&tabs=visual-studio

to add google see:

https://learn.microsoft.com/en-us/aspnet/core/security/authentication/social/google-logins?view=aspnetcore-8.0