JSON Web Encryption (JWE) in .NET Core


A signed JSON Web Token (JWT) is one of the most useful and common constructs you’ll see floating around modern security systems. These tokens give us a simple, secure structure in which to transfer data and verify that it has not been tampered with. However, what about when we need to send sensitive data within a JWT?

To solve this issue, we have JSON Web Encryption (JWE), enabling us to encrypt a token so that only the intended recipient can read it.

In this article, we’re going to look at how we can protect sensitive data within our JWTs in .NET Core, using JWEs and the various token libraries available to us.

Skip to code.

.NET Core

JWE Format

We’re going to use JWE Compact Serialization (as opposed to JWE JSON Serialization), which looks something like the following:


Encrypted JWTs comprise of 5 sections:

JWE Protected Header

This is the header of the JWE itself, describing the wrapped token:


Which, when base64 decoded has the value of:

  "alg": "http://www.w3.org/2001/04/xmlenc#rsa-oaep",
  "enc": "A128CBC-HS256",
  "kid": "6B7ACC520305BFDB4F7252DAEB2177CC091FAAE1",
  "typ": "JWT"

Here, our algorithm (alg) value is http://www.w3.org/2001/04/xmlenc#rsa-oaep, which describes how the Content Encryption Key (CEK) was encrypted. The encryption algorithm (enc) value is A128CBC-HS256, which is how the plaintext was encrypted using the CEK. This encryption algorithm must allow for authentication encryption.

In this instance, the Key ID (kid) value references the public key that was used to encrypt the data.

Check out the JWE specification for further header parameters.

JWE Encrypted Key

This is the Content Encryption Key (CEK), a symmetric key that was generated to encrypt the plaintext, and then itself encrypted using the recipients public key (using the algorithm in the header (http://www.w3.org/2001/04/xmlenc#rsa-oaep)). This is known as key wrapping.


JWE Initialization Vector

The initialization vector used when encrypting the plaintext:


JWE Ciphertext

The plain text, protected using authenticated encryption using our encryption algorithm (A128CBC-HS256), with the CEK as the encryption key, the JWE initialization vector, and the “Additional Authenticated Data”, which when using compact serialization, is the encoded JWE protected header:


Which, when decrypted, looks like:


JWE Authentication Tag

As a result of performing authenticated encryption, we also receive an authentication tag:


This value is then used during decryption, to ensure integrity (the same value is outputted as a result of decryption).

To find out more about JWEs, check out RFC7516.

JWE Tokens in .NET Core

The first thing we’ll need is the latest version of `System.IdentityModel.Tokens.Jwt`:

install-package System.IdentityModel.Tokens.Jwt

Creating a JWE Token

We can now use JwtSecurityTokenHandler just like we normally would, but this time supplying some EncryptingCredentials. This is the public key of the recipient (whoever needs to read the token).

var handler = new JwtSecurityTokenHandler();

var tokenDescriptor = new SecurityTokenDescriptor { Audience = "you", Issuer = "me", Subject = new ClaimsIdentity(new List<Claim> {new Claim("sub", "scott")}), EncryptingCredentials = new X509EncryptingCredentials(new X509Certificate2("key_public.cer")) };
string token = handler.CreateEncodedJwt(tokenDescriptor);

By default, X509EncryptingCredentials will use a key wrapping algorithm of http://www.w3.org/2001/04/xmlenc#rsa-oaep and an encryption algorithm of A128CBC-HS256 (AES-128-CBC with HMAC-SHA256 for authentication). The JWE specification typically uses AES-256-GCM, but GCM support in .NET is a bit patchy. GCM support should be with us in .NET Core 3.0. If you want to override these defaults, there’s overrides on the X509EncryptingCredentials.

Reading a JWE Token

To read the encrypted JWT, we need to have the corresponding private key to the public key that was used to encrypt it:

var handler = new JwtSecurityTokenHandler();
var claimsPrincipal = handler.ValidateToken(
	new TokenValidationParameters
		ValidAudience = "you",
		ValidIssuer = "me",
		RequireSignedTokens = false,
		TokenDecryptionKey = new X509SecurityKey(new X509Certificate2("key_private.pfx", "idsrv3test"))
	out SecurityToken securityToken);

Here we get access to both the parsed security token and a claims principal that represents the token’s payload.

That’s all there is to it!

Scott Brady

Scott Brady

Scott Brady is the Identity & Access Control Lead at Rock Solid Knowledge, focusing on authentication, OAuth and OpenID Connect.

Keep Up To Date

Sign up to the mailing list to keep up to date with the latest articles and announcements.