Expired JWT token triggers 401 in Angular HttpInterceptor without automatic redirect or refresh
Goal: Ensure that Angular applications enforce least‑privilege access through route guards while gracefully handling expired JWT credentials. Constraints: Route guards execute synchronously; any asynchronous token validation must return a Promise or Observable, which can affect navigation timing. An HttpInterceptor can detect 401 responses, but automatically
angular