JWT - Verifier Node
| Description | The JWT - Verifier node validates an incoming JWT to ensure its authenticity and integrity. |
| Available in | Authentication, Admin, Self Service, API, Consent, Library, Custom, User Defined |
| Node Name | JWT - Verifier |
Node Configurations
JWT
Specifies the JWT to be verified. #### Load by URL JWT can be retrieved from a specified URI. This allows loading the token from an external source. In this case defines the **time-to-live (in seconds)** for the retrieved JWT.Choose Signature type
Enables signing of the JWT to ensure integrity and authenticity. ### JWK Configuration - **Symmetric Key (Password)**: Uses a shared secret (**HS256, HS384 or HS512**) - **Asymmetric Key**: Uses public/private key pairs (**RSA or EC**)Symmetric Key
#### KID Unique identifier of the key used to sign the token. It is included in the JWT header. #### OCT Algorithm Defines the signing algorithm (e.g., HS256, HS384, HS512). #### Password The secret (for symmetric) or key material (for asymmetric signing). #### JWK JSON representation of the key. Can be auto-generated or manually edited.Asymmetric Key
#### Asymmetric Key Type Can choose between RSA and EC algorithm. #### KID Unique identifier of the key used to sign the token. #### Key Size In case of RSA key defines the size of the RSA key in bits (e.g., 2048, 4096). #### RSA Algorithm In case of RSA key, specifies the RSA based signing algorithm to use (e.g., RS256, RS384, RS512). #### EC Algorithm In case of EC key, specifies the EC based signing algorithm to use (e.g., ES256, ES384, ES512). #### Curve In case of EC key, defines the elliptic curve used for EC-based cryptographic operations. #### Public Key The public key used to verify the JWT signature. #### Public JWK The Public JWK represents the public key in JSON Web Key (JWK) format.Choose Encryption type
Enables encryption of the JWT (JWE) to add an extra layer of security. ### JWK Configuration - **Symmetric Key (Password)**: Uses a shared secret (**A128KW, A256KW etc.**) - **Asymmetric Key**: Uses public key (**RSA or EC**)Symmetric Key
#### KID Unique identifier of the key. #### OCT Algorithm Defines the signing algorithm (e.g., A128KW, A256KW). #### Password The secret (for symmetric) or key material (for asymmetric signing). #### JWK JSON representation of the key. Can be auto-generated or manually edited.Asymmetric Key
#### Asymmetric Key Type Can choose between RSA and EC algorithm. #### KID Unique identifier of the key. #### Key Size In case of RSA key defines the size of the RSA key in bits (e.g., 2048, 4096). #### RSA Algorithm In case of RSA key, specifies the RSA based encryption algorithm to use (e.g., RSA-OAEP, RSA-OAEP-256). #### EC Algorithm In case of EC key, specifies the EC based encryption algorithm to use (e.g., ECDH-ES, ECDH-ES+A128KW). #### Curve In case of EC key, defines the elliptic curve used for EC-based cryptographic operations. #### Private Key The private key used to sign the JWT. This key must be kept secure and never exposed publicly. #### Public Key The public key used to verify the JWT signature. #### Public JWK The Public JWK represents the public key in JSON Web Key (JWK) format. #### Private JWK The Private JWK represents the private key in JSON Web Key (JWK) format.Save in the Flow store
Save in the Flow store
Attributes generated or retrieved from the node can be saved **into a variable**. They can then be **reused by other nodes** in the flow by referencing them as `{{variable.attribute}}`. To do this you choose attributes that need to be stored in the variable, and in the flow store (All attributes exposed by the node are listed in a **multi-select dropdown**, allowing the user to choose **one or more** of them), then a **variable name** that can be **freely defined** by the user. There is also a flag to make the variable available to the **frontend**.Default Output Node
- True
- Not Verified
- Expired
- Failure
