1. Unleash Core Cryptographic Power
The Crypto node is the ultimate security layer for any HTTP Request Node integration. It empowers you to handle sensitive data with absolute confidence.
- Hash (One-Way): Instantly convert your input into an irreversible fixed-length string using advanced algorithms like SHA3-512 and BLAKE2b.
- Sign (HMAC): Effortlessly generate a cryptographic signature. This is strictly required by Payment Gateways (Stripe, PayPal) and secure webhook providers.
- Encrypt & Decrypt: Surgically lock and unlock your data using the ultra-secure
AES-256-GCMsymmetric algorithm.
2. Advanced JWS & JWE Cryptography
For high-security API integrations (like Apple Pay, Open Banking, or OIDC Identity Providers), aggressively leverage JSON Web Token standards.
- JWS (JSON Web Signature): Seamlessly sign payloads using HS256 or RS256 to guarantee data integrity and authenticity.
- JWE (JSON Web Encryption): Encrypt sensitive payloads using RSA-OAEP and A256GCM. Only the possessor of the Private Key can decrypt and read the token.
3. Bulletproof Bcrypt Authentication
Modern systems must abandon outdated Hash algorithms (MD5, SHA) for password storage to prevent Rainbow Table attacks. Unleash native Bcrypt support directly in your workflow.
- Hash Password: Automatically generates a random salt and hashes the plaintext password into a highly secure string.
- Verify Password: Compares a plaintext password against the hashed string stored in your Database. It outputs a simple
trueorfalseboolean.
Frequently Asked Questions (FAQ)
When should I use JWE instead of JWS?
Use JWS when you only need to prove who sent the data (Integrity). Use JWE when the data itself is highly confidential (like credit card tokens) and must be completely hidden (Confidentiality).
Why use BLAKE2b or SHA3 over SHA256?
BLAKE2b and SHA3 are modern hashing algorithms that offer significantly higher security margins and hardware performance than older SHA2 algorithms. They surgically prevent advanced collision attacks.
