Integrate Hanko with PasskeysStrategy of nestjs！

[arcsin1]

import { ExtractJwt, Strategy } from 'passport-jwt';
import { PassportStrategy } from '@nestjs/passport';
import { Injectable, } from '@nestjs/common';
import { ConfigService } from '@nestjs/config';
import type { Request } from 'express';
import * as jwksRsa from 'jwks-rsa';


@Injectable()
export class PasskeysStrategy extends PassportStrategy(Strategy, 'passkeys') {
  constructor(
    private readonly configService: ConfigService,
  ) {
    const jwksHost = configService.get('jwt_uri');
    super({
      jwtFromRequest: ExtractJwt.fromExtractors([
        (req) => req.cookies['hanko'],
      ]),
      secretOrKeyProvider: jwksRsa.passportJwtSecret({
        cache: true,
        rateLimit: true,
        jwksRequestsPerMinute: 2,
        jwksUri: `${jwksHost}/.well-known/jwks.json`,
      }),
      algorithm: ['RS256'],
      ignoreExpiration: true,
      passReqToCallback: true,
    });
  }

  async validate(req: Request, payload: any) {
 // do anything
 // aud: [ 'localhost' ],
  // exp: 1699005014,
  // iat: 1699001414,
  // sub: '66rer6-6664-44-44fefreg'

    console.info(payload);


    return payload

  }
}

[kalinchernev]

Although Hanko is full speed on passkeys, why "passkeys" and passport?
To what I can see from their example https://github.com/teamhanko/hanko-react-express-starter/blob/main/express-server/middleware/validateTokenHandler.js it's indeed the "hanko" cookie req.cookies['hanko'] which is a JWT (ok for ExtractJwt.fromExtractors) but why so many abstractions?

It seems to me jose + a regular Nest guard would suffice, IDK