Decrypt then verify nested JWE(JWS)

Performs decrypt-then-verify operation: decrypts nested JWE to reveal inner JWS,
then verifies the signature and extracts original plaintext.

Decryption and verification key identifiers are automatically extracted from
token headers per JOSE standards (RFC 7516 §4.1.4, RFC 7515 §4.1.4).

Both keys must be homogeneous (both symmetric or both asymmetric). COMPOSITE
keys are supported via JWE/JWS General JSON Serialization format.

Key type combinations:

  • Symmetric + Symmetric (e.g., AES-GCM + HMAC-SHA256)
  • Asymmetric + Asymmetric (e.g., ML-KEM + ML-DSA, RSA + RSA)
  • COMPOSITE + COMPOSITE (e.g., COMPOSITE_KEM_COMBINE + COMPOSITE_SIGNATURE)
  • COMPOSITE + SIMPLE (any homogeneous combination)

Returns 422 if signature verification fails or token format is invalid.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Nested JWE token containing signed JWS payload

Request body for the decrypt-then-verify operation: unwraps a nested JWE-of-JWS payload.

jweToken
object
required

Outer JWE General JSON Serialization (RFC 7516 §7.2) containing
an inner JWS payload. Decryption and verification kids are
extracted automatically from the JWE protected header and the
inner JWS protected header per RFC 7515/7516 standards.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json