JWT Verify
Category: Authentication
Status: Registered and callable in the CyberChef 11.3.0 compatibility inventory.
Input / output: string → JSON
Background: https://wikipedia.org/wiki/JSON_Web_Token
What it does
Verifies that a JSON Web Token is valid and has been signed with the provided secret / private key. The key should be either the secret for HMAC algorithms or the PEM-encoded public key for RSA and ECDSA.
Note
Status here means the operation name is implemented and callable. It does not by itself promise byte-for-byte parity for every upstream option. See Compatibility and current status for the verified scope and known boundaries.
Arguments and options
Arguments are positional. Keep their order when using bake() or
Pipeline.then().
Index |
Name |
UI type |
PyChef default |
Accepted values / format |
|---|---|---|---|---|
|
Public/Secret Key |
|
|
|
Recipe template
Important
This is a call template built from the documented defaults. Replace placeholder values such as empty keys, paths, patterns, or lookup data before running it.
from pychef import bake
input_value = "example"
args = ['secret']
result = bake(input_value, [{"op": 'JWT Verify', "args": args}])
print(result)
Pipeline example
from pychef import Pipeline
args = ['secret']
transform = Pipeline().then('JWT Verify', *args)
result = transform("example")
Dedicated operation module
The registered entry point lives in
pychef.operations.by_operation.jwt_verify. Direct calls
receive the input value and a positional argument tuple:
from pychef.operations.by_operation.jwt_verify import run
result = run("example", tuple(['secret']))
- pychef.operations.by_operation.jwt_verify.run(value, args)
Run this operation using its shared internal implementation.
- Parameters:
value (str | bytes)
args (Sequence[Any])
- Return type:
str | bytes