Angular 7自动刷新不记名令牌

daf*_*daf 4 authorization interceptor jwt bearer-token angular

我有一个 AuthService,主要有两种方法:

  • getAuthToken(返回 Promise,因此可以延迟调用/在单个集合上阻塞等待多次调用)

  • refreshToken(还返回一个 Promise,使用原始 JWT 上可用的刷新令牌来请求新的身份验证令牌)

我想自动

  • 将不记名令牌应用于每个 http 请求(工作)
  • 刷新时刷新令牌——我已经快到了,只是使用刷新令牌的请求结果不会返回到原始订阅者。

这是代码:

import { HttpEvent, HttpHandler, HttpHeaders, HttpInterceptor, HttpRequest } from "@angular/common/http";
import { from, Observable } from "rxjs";
import { Injectable } from "@angular/core";
import { AuthService } from "./auth.service";

@Injectable()
export class AuthHttpInterceptor implements HttpInterceptor {
  constructor(
    private _authService: AuthService,
  ) {
  }

  intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
    return from(this.addBearerToken(req, next));
  }

  private async addBearerToken(req: HttpRequest<any>, next: HttpHandler): Promise<HttpEvent<any>> {
    const token = await this._authService.getAuthToken();

    const headerSettings = req.headers.keys().reduce(
      (acc, cur) => {
        acc[cur] = req.headers.getAll(cur);
        return acc;
      }, {});

    if (token) {
      headerSettings["Authorization"] = `Bearer ${ token }`;
    } else {
      console.log("performing request without auth!");
    }
    // prevent 302 redirect to challenge on a 401
    headerSettings["X-Requested-With"] = "XMLHttpRequest";
    const
      headers = new HttpHeaders(headerSettings),
      newRequest = req.clone({ headers });
    const result = next.handle(newRequest).toPromise();
    result.catch(async (err) => {
      if (err.status === 401) {
        const
          newToken = await this._authService.refreshToken();
        headerSettings["Authorization"] = `Bearer ${ newToken }`;
        const
          updatedHeaders = new HttpHeaders(headerSettings),
          updatedRequest = req.clone({ headers: updatedHeaders });
        console.log("requery with new token"); // <-- I see this when I have a 401, eg by altering the auth token to be bad, whilst leaving the refresh token alone
        return next.handle(updatedRequest).toPromise().then(data => {
          console.log("requeried data:", data); // <-- I also see this fire, with the valid data coming back from the second request
          return data; // <-- however the original caller doesn't get this data
        });
      }
    });
    return result;

  }
}
Run Code Online (Sandbox Code Playgroud)

我必须假设这可能是由于我混合了 Observables 和 Promises(我这样做是因为 AuthService 是异步的,使用 Promises)。另外,如果没有 401,原始调用确实会正确通过——就好像承诺链在该行之后被删除一样

next.handle(newRequest).toPromise();
Run Code Online (Sandbox Code Playgroud)

我缺少什么?

yur*_*zui 5

你在这里打破了链条:

const result = next.handle(newRequest).toPromise();
result.catch(async (err) => {
  ...
});

return result;
Run Code Online (Sandbox Code Playgroud)

result.catch返回一个新的 Promise,并且您的处理程序不会等待您在 内部调用的所有操作catch

所以你可以这样写:

const result = next.handle(newRequest).toPromise();
return result.catch(async (err) => {
  ...
});
Run Code Online (Sandbox Code Playgroud)

另外,您可能想要做的就是在进行时不要多次调用刷新令牌

cachedRequest: Promise<any>; // define prop in your class
...

if (!this.cachedRequest) {
  this.cachedRequest = this.authService.refreshToken();
}
const  newToken = await this.cachedRequest;
this.cachedRequest = null;
Run Code Online (Sandbox Code Playgroud)

这是一个简单的演示,您可以测试一下。(我在那里处理404,但这并不重要