Skip to content

Backend Integrations

AuthAction issues JWT access tokens that your backend APIs can validate using standard JWKS-based verification. This section provides integration guides for popular backend frameworks.

  • Express.js — JWT middleware with express-jwt and jwks-rsa
  • NestJS — Passport JWT strategy with JWKS validation
  • Spring Boot — Spring Security OAuth2 Resource Server
  • Go — Gin middleware with golang-jwt and jwx
  • .NET — ASP.NET Core JWT Bearer authentication
  1. Your frontend obtains an access token from AuthAction
  2. The frontend sends the token in the Authorization: Bearer <token> header
  3. Your backend validates the token’s signature against AuthAction’s JWKS endpoint
  4. If valid, the request is authorized; otherwise a 401 Unauthorized response is returned

All implementations validate the issuer, audience, and RS256 signature of the JWT to ensure the token is legitimate and intended for your API.