liveBook · Manning

Ciphertext

As explained in Secure APIs

Ciphertext is data produced by encrypting plaintext so that it is not readable without the required decryption capability.

Ciphertext is the unreadable result of encrypting plaintext. In authenticated encryption, it is accompanied by an authentication tag that helps detect modification of the ciphertext or protected additional data. section 7.2.2

JSON Web Encryption (JWE) uses ciphertext to protect sensitive token contents, such as access-token claims. A JWE also carries an encrypted key, initialization vector, protected JOSE header, and authentication tag. section 7.2.2

Ciphertext inside a JWE

A compact JWE represents its parts as Base64url-encoded protected header, encrypted key, initialization vector, ciphertext, and authentication tag, separated by periods. A JSON serialization uses fields such as "ciphertext" and "tag".

How Secure APIs covers it

How deep it goes
Defines ciphertext and places it within JWE structure, but does not explain encryption algorithms internally.
Examples
Uses compact and JSON JWE representations containing ciphertext alongside encrypted keys, initialization vectors, headers, and tags.
What it assumes
Assumes only the distinction between plaintext and encrypted data, defining both within the explanation.
What you can do after
Evaluate how encrypted token data and integrity metadata are represented in a JWE.
How it connects
Connects ciphertext with plaintext, authenticated encryption, authentication tags, JWE, JWT, and JOSE headers.
Cover of Secure APIs
liveBookmanning.com
Read Secure APIs on liveBook Get the book at manning.com

Also explained in

Compare how 5 books explain ciphertext →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.