API keys are the right fit for server-to-server APIs where full OAuth is overkill. Three ways to enforce one in ASP.NET Core - middleware, an MVC filter, and a minimal API endpoint filter - and when each fits.
Put roles in the JWT, seed them with Identity, and gate endpoints with RequireRole - plus refresh tokens in HttpOnly cookies so the whole flow works from a browser.
Let users sign in with Google using ASP.NET Core's own authentication middleware - a server-driven redirect flow through AddGoogle, converted into the same JWT + HttpOnly refresh-token cookies a regular email/password login gets.
Hand-roll a full JWT authentication flow on .NET 9 - ASP.NET Core Identity for user storage, roles baked into the access token, and a refresh token stored in an HttpOnly cookie so a browser client stays signed in without touching localStorage.
A JWT sitting in memory does not stop a signed-out user from seeing a protected page for a split second. An Angular functional route guard, paired with a .NET Identity + refresh token backend, closes that gap.
Wire ASP.NET Core Identity's built-in API endpoints to an Angular app - login, a bearer token on every request, and an HTTP interceptor that silently refreshes an expired token and retries the failed call.