Create or check a password?
Generate when no credential exists; validate strength or compare with a stored hash when checking one.
Elysia Tools
Navigation
Workflow Playbook
Generate or validate password credentials and inspect JWT security signals without treating key pairs as passwords.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Password Generator
Hubs
| Tool | What it does | Category |
|---|---|---|
| Password Generator | Generate secure random passwords | Security |
| Password Validator | Validate password strength and check against common security requirements | Security |
| Strong Password Validator | Validate password strength against common security requirements (uppercase, lowercase, numbers, special chars, length) | Validation |
| Bcrypt Generator | Generate bcrypt hash from password | Cryptography |
| Bcrypt Validator | Validate password against bcrypt hash |
Hubs
| Cryptography |
| PBKDF2 Generator | Generate PBKDF2 key derivation hash | Cryptography |
| PBKDF2 Validator | Validate password against PBKDF2 derived key | Cryptography |
| Scrypt Generator | Generate Scrypt hash from password | Cryptography |
| Scrypt Validator | Validate password against Scrypt derived key | Cryptography |
| JWT Generator | Generate JWT tokens with custom claims and algorithms | Security |
| JWT Decoder | Decode JWT tokens | Security |
| JWT Decoder & Security Auditor | Decode JWT header and payload, verify HS256 or RS256 signatures, and flag algorithm, expiry, and sensitive-claim security risks | Security |
Generate or validate password credentials and inspect JWT security signals without treating key pairs as passwords.
Use this guide to turn the stated scope into a reviewable result. Keep the source, intermediate outputs, and decisions together so the next person can understand what was checked and why.
Use synthetic passwords, hashes, and JWTs rather than production secrets.
Identify whether the task is generation, password verification, token decoding, or security review.
Decision: Create or check a password?. Generate when no credential exists; validate strength or compare with a stored hash when checking one.
Decision: Decode or audit a token?. Decode for header and payload; audit for algorithm, signature, expiry, and sensitive-claim findings.
Decision: Is this a key or TLS task?. Keep private-key generation and certificate inspection outside this password and JWT workflow.
Generate a non-production password candidate. Use password-generator.
Apply the matching password policy validators. Use password-validator, strong-password-validator.
Compare a candidate with a matching derived hash. Use bcrypt-generator, bcrypt-validator, pbkdf2-generator, pbkdf2-validator, scrypt-generator, scrypt-validator.
Create a JWT with known test claims. Use jwt-generator.
Decode structure, then audit security signals. Use jwt-decoder, jwt-decoder-security-auditor.
Workflow playbook
Generate a non-production password candidate.
Apply the matching password policy validators.
Compare a candidate with a matching derived hash.
Create a JWT with known test claims.
Decode structure, then audit security signals.
Generate when no credential exists; validate strength or compare with a stored hash when checking one.
Decode for header and payload; audit for algorithm, signature, expiry, and sensitive-claim findings.
Keep private-key generation and certificate inspection outside this password and JWT workflow.