Registry / security / n8n-nodes-leodelivery-system-auth

n8n-nodes-leodelivery-system-auth

JSON →
library1.0.2jsnpmunverified

A community node for n8n that generates JWT tokens (HS256) to authenticate with the LeoDelivery system. Version 1.0.2 is the current stable release. The node requires an n8n instance with community node support, and the JWT secret is configured via a dedicated credential type. It supports configurable token properties such as expiration, role, subject, name, and user type. This node is specifically tailored for LeoDelivery and not a general JWT utility.

npm install n8n-nodes-leodelivery-system-auth
INSTALL
IMPORT
SIG · N8N-NODES-LEODELIV
N
n8n-nodes-leodelivery-system-auth
securityjavascriptv1.0.2
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

LeoDeliverySystemAuth
import { LeoDeliverySystemAuth } from 'n8n-nodes-leodelivery-system-auth'
const LeoDeliverySystemAuth = require('n8n-nodes-leodelivery-system-auth')
ESM-only package; CommonJS require will not work. TypeScript types are included.
JwtSecretApi
import { JwtSecretApi } from 'n8n-nodes-leodelivery-system-auth'
import { JwtSecretApi } from 'n8n-nodes-leodelivery-system-auth/credentials'
The credential class is exported from the main entry, not a subpath. Use named import.
type IAuthNodeOptions
import type { IAuthNodeOptions } from 'n8n-nodes-leodelivery-system-auth'
import { IAuthNodeOptions } from 'n8n-nodes-leodelivery-system-auth'
IAuthNodeOptions is a TypeScript type; import it using import type to avoid runtime errors. Not exported in CJS.

Shows how to install, configure credentials, and use the LeoDelivery System Auth node in n8n to generate a JWT token.

// This node is used within the n8n UI; example workflow setup: // 1. Install the node via n8n community nodes (Settings > Community Nodes > Install > n8n-nodes-leodelivery-system-auth) // 2. Create a credential of type 'JWT Secret API' with your secret key // 3. Add a 'LeoDelivery System Auth' node to the canvas // 4. Configure parameters: Expiration In Seconds (e.g., 3600), Role (e.g., 'admin'), Subject, Name, User Type // 5. Connect it to an HTTP Request node or other nodes to use the generated token // The node outputs the token as a string in the `token` field.
Debug
Known issues
gotchaThis node only supports HS256 algorithm. If your LeoDelivery system expects a different algorithm (e.g., RS256), the generated token will be rejected.
fix
Ensure your LeoDelivery system's JWT validation expects HS256 tokens. If not, use a different JWT node.
affects: all
gotchaThe JWT secret is stored in plaintext within the n8n credential store. Ensure your n8n instance is secured and access to credentials is restricted.
fix
Restrict access to the n8n credentials UI and database. Consider using n8n's built-in encryption for credentials.
affects: all
deprecatedThe credential type 'JWT Secret API' may be renamed in future versions. Check the node documentation for any credential type changes.
fix
Monitor the node's changelog for credential type updates and migrate accordingly.
affects: >=1.0.0
gotchaToken expiration is configured in seconds. Providing a very large value may create a token that never expires, which is a security risk.
fix
Set expiration to a reasonable value (e.g., 3600 for one hour) based on your application's needs.
affects: all
Errors
Common errors & fixes
Error: Cannot find module 'n8n-nodes-leodelivery-system-auth'
The node is not installed correctly or n8n's community node cache needs refresh.
fix
Reinstall the node via n8n UI (Settings > Community Nodes > Uninstall, then Install again) or restart the n8n server.
TypeError: n8nNodesLeodeliverySystemAuth is not a constructor
Using CommonJS require instead of ESM import.
fix
Ensure your n8n instance uses ESM (modern n8n versions support ESM). Use import syntax if writing custom code.
401 Unauthorized when using generated token
The JWT secret provided in credentials does not match the LeoDelivery system's expected secret, or the token has expired.
fix
Verify the secret key is correct. Check that the token expiration time is aligned with the server's clock. If the system uses a different algorithm, this node cannot be used.
JWT_SECRET_API credential type not found
The node or its credential definition is not loaded properly.
fix
Ensure the node is installed and n8n has been restarted. Check that the package.json exports the credential correctly.
Upgrade
Version history
1.0.2latest on npm
Audit
Dependencies
n8n-workflowrequiredPeer dependency for node base classes
Agent activity
8 hits · last 30 days
node
8
Resources
n8n-nodes-leodelivery-system-auth — npm install n8n-nodes-leodelivery-system-auth · libregistry