npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-jwks

v0.0.3

Published

Provides ability to work with JSON Web Key Sets (JWKS).

Readme

JWKS Node

The JWKS Node for n8n enables you to fetch JSON Web Key Sets (JWKS) from a remote endpoint and verify JSON Web Tokens (JWTs) directly within your workflow. JWKS is a standard for representing cryptographic keys in a JSON structure, commonly used for JWT verification.

Features

  • Fetch JWKS from a URL
  • Verify JWTs using the keys from the JWKS endpoint
  • Cache keys for efficient repeated verification
  • Integrate authentication and authorization into your n8n workflows

Usage

  1. Add the JWKS Node to your n8n workflow.
  2. Configure JWKS Credentials: In the credentials section, enter the endpoint where your JWKS is hosted (e.g., https://example.com/.well-known/jwks.json).
    You can also set additional verification options such as issuer, audience, subject, max token age, clock tolerance, and required claims in the credentials.
    These options can be overridden per node execution.
    See JWKS Credentials for details.
  3. Provide the JWT: Supply the JWT you want to verify as an input to the node.
  4. Receive verification results: The node outputs the decoded JWT payload if verification succeeds.

Example Output

{
  "verified": true,
  "payload": {
    "sub": "user123",
    "exp": 1712345678,
    "iat": 1712341678
  }
}

JWKS Credentials

The JWKS Node requires the following credentials to connect and verify JWTs:

  • URL: The HTTPS endpoint where your JWKS (JSON Web Key Set) is hosted.
    Example: https://example.com/.well-known/jwks.json
  • Issuer (optional): The expected issuer (iss) of the JWT.
    Can be overridden in the node.
  • Audience (optional): The expected audience (aud) for the JWT.
    Can be overridden in the node.
  • Subject (optional): The expected subject (sub) of the JWT.
    Can be overridden in the node.
  • Max Token Age (optional): The maximum age of the JWT.
    Can be overridden in the node.
    • In seconds when a number (e.g. 5)
    • Resolved into a number of seconds when a string (e.g. "5 seconds", "10 minutes", "2 hours")
  • Clock Tolerance (optional): Allowed clock skew when verifying the JWT.
    Can be overridden in the node.
    • In seconds when a number (e.g. 5)
    • Resolved into a number of seconds when a string (e.g. "5 seconds", "10 minutes", "2 hours")
  • Required Claims (optional): List of claims that must be present in the JWT payload.
    Can be overridden in the node.
    • Default behavior:
      • If the issuer option is set, then JWT "iss" (Issuer) claim must be present
      • If the audience option is set, then JWT "aud" (Audience) claim must be present
      • If the subject option is set, then JWT "sub" (Subject) claim must be present
      • If the maxTokenAge option is set, then JWT "iat" (Issued At) claim must be present

These fields are configured in the credentials UI when you add the JWKS Node to your n8n workflow.

References