fastify-oauth2 VS fastify-jwt

There were several options on the table, but 2 options were more serious than the others. The first option is to use the @fastify/fastify-oauth2 package. The second option is to use Google Auth Library.

You can just use the fastify-oauth2 plugin https://github.com/fastify/fastify-oauth2. Of course, you first have to set up your login providers.

Let me explain it again. The banlist is mean to inspect the payload/claims and deny access even if the signature/JWT is valid. We don't need to change anything else. A lot of libraries already provide such a feature. For example https://github.com/fastify/fastify-jwt via the trusted preHook.

Hey, thanks for the reply. I'm doing a port from another stack, and that app's implementation is using using the Okta SAML integration. I see how to secure my app's endpoints without issue, but the question I've got comes in with the actual login workflow. Okta's documentation (link) is exclusively focusing on Express + Passport for the OIDC option. Fastify's ecosystem (link) has fastify-auth + fastify-jwt. But I don't see a SAML implementation, which is where I originally was intending to go because the idp is already set up and tested.