Give us feedback
jwt
Service icon

JWT

Stable version 4.1.1 (Compatible with OutSystems 11)
Other versions available for 10
Uploaded on 3 Jul (13 days ago) by 
4.5
 (17 ratings)
jwt

JWT

Details
Library for creating, decoding and validating JSON Web Tokens, an open, industry standard RFC 7519 method for representing claims securely between two parties.
Read more

Library to handle JSON Web Tokens used in server-side OAuth authentication. Currently this component allows generating and decoding tokens, which are needed to connect to existing REST services that require JWT for authentication. It supports tokens signed symmetrically (using HS256, HS384, HS512) and also asymmetrically (using RS256, RS384, RS512).


Note:

Follow your API's documentation on how to enable and authenticate using JWT. For public REST services an asymmetric key probably is needed and each service may require further claims besides the mandatory ones.

------------------------------------------------------------------------------

Currently, this component doesn’t support the following algorithms: ES256, ES384 and ES512 

------------------------------------------------------------------------------

Features list:

Generate a JSON Web Token (JWT)

Generate a token using a plain secret key as signature (symmetric).

Generate a token using a private key  (PEM file) as signature (asymmetric).

Generate a token using a JSON Web Key (JSON object) as signature.

Generate an unsigned token.


Read a JSON Web Token (JWT)

Read a token generated using the plain secret key.

Read a token generated using the public key (of generated PEM file).

Read a token generated using a public key (Json Web Key).


Get a JSON Web Key (JWK, public key) from a JSON Web Key Sets (JWKS)

Helper action to obtain the JWK from a JWKS.

 



On the roadmap

  • Suport for ES256, ES384 and ES512 
  • Custom fields in header
  • Support for binary keys
  • Nested claims
  • multiple audiences
Release notes (4.1.1)

Updated BouncyCastle.Cryptography 2.3.1 to 2.4.0 (latest stable)

Recommended to deploy on Platform 11.19.0 or later

License (4.1.1)
Reviews (3)
by 
3 May
in version 4.0.6
It works perfectly for creating a Signed Asymmetric Token from PemKey using a GCP serving account (no passphrase/password is needed, I posted an example in the community forum)
by 
23 Feb
in version 4.0.6
It sucks , you cannot create the JWT without Passphrase key if you use the Asymmetric RS256 method and google service account is such a example that you can never create a JWT with it
Answer from the owner
23 Feb
in version 4.0.6
Have you tried to post something here in Support? Have you tried report the issue properly? Have you tried to reach out to the team?...
by 
2023-02-16
in version 4.0.6
Its working fine as expected.
Team