Feature Request: Hide or Disable Specific ASP.NET Core Identity Endpoints and Return Bearer Tokens via SignInManager

[KMastalerz]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

I've been searching for documentation and solutions, but I couldn't find anything from Microsoft regarding hiding or disabling specific ASP.NET Core Identity endpoints. My use case is as follows:

Hide Default Identity Endpoints: I would like to use my own custom registration process and prevent exposure of the default Identity registration endpoint. While I know that I can override or replace these endpoints by creating extensions, I’m wondering if there is a built-in way to disable or hide specific Identity endpoints without manual intervention.

SignInManager and Bearer Token Support: I am also considering creating a custom login flow using SignInManager. However, I have noticed that SignInManager does not support generating and returning bearer tokens. It requires manual token generation and additional configuration for authentication, which can be cumbersome and this is tomething I wanted to avoid.

It would be useful if SignInManager could optionally return bearer tokens directly upon successful login, avoiding the need for developers to handle token generation and authentication configuration separately. This would simplify development in cases where we want to use ASP.NET Core Identity but prefer not to handle token generation ourselves. But also would not limit us, to create out own Tokens when we do not want to.

Describe the solution you'd like

Provide a way to hide or disable specific ASP.NET Core Identity endpoints, such as registration, login, etc., either through configuration or built-in mechanisms.

Add support for returning bearer tokens directly via SignInManager without requiring manual token generation and configuration.

Additional context

I want to Login with phone/email/login but also other thru other contexts, like customed ID, although this one is for desktop app. This is due to how original application had worked.

Im creating my own Registration endpoint, since I want more details to be required on registration. Including my own User table fields.

[MackinnonBuck]

The ability to map identity endpoints separately is tracked by #55792.

SignInManager does support generating Bearer tokens - see https://learn.microsoft.com/aspnet/core/security/authentication/identity-api-authorization#use-token-based-authentication.

Does this meet your needs? If not, could you elaborate on what additional requirements you have?

[dotnet-policy-service]

Hi @KMastalerz. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.